I am trying to install the WCF data services from
http://www.microsoft.com/downloads/details.aspx?familyid=79d7f6f8-d6e9-4b8c-8640-17f89452148e&displaylang=en
However, I only get the error message: "the update is not applicable to your computer".
I am using Windows 7 with .NET 3.5 SP1/.NET 4.0 installed.
Do you have the same problem?
This update requires .NET 3.5 SP 1 - do you already have SP1 ?? If not - first get the .NET 3.5 Service Pack 1 and install that.
UPDATE: ok, so you do have .NET 3.5 SP1 installed - could the presence of .NET 4 cause your problems? Can you try on a second machine (or in a VM) with only .NET 3.5 SP1 installed?
Related
I have asp .net 4 application running in development (local) on windows 8.1 & Visual Studio 2013, installed .net framework version 4.5, IIS Express
The production server is setup with windows server 2003 and installed .net framework version 4.0, IIS 6
The web application Target Framework is .net framework 4
Lately i have encountered SqlException (0x80131904): "Some part of your SQL statement is nested too deeply".
This exception occurs only in production (on windows server 2003) where the runtime version is 4.0.30319.1022
In development (local on windows 8.1) where the runtime version is 4.0.30319.34011 this exception does not occur.
The SQL generated by LINQ in the server is different than the SQL generated in the local.
After a little research i found that different version of .net is causing this behavior.
As far as i know, the difference between the two versions is:
version 4.0.30319.1022 is built on .net framework 4.0 and version 4.0.30319.34011 is built on .net framework 4.5
Since .net framework 4.5 is not supported on windows server 2003, I would require targeting the older version on my dev machine.
Is there a way to target my dev instance to use the exact same .NET framework version or entities dll that is used in order to receive the same behavior in both dev & prod instances?
Thanks in advance,
Shai
I'm about to install .net 4.5 on a windows 2008 server with .net 2.0 and .net 4.0 already installed. I also have over 10 web forms applications running on iis. Microsoft said that the in-place installation of 4.5 over 4.0 is completely backwards compatible, but I still want to know if I should have any other concerns before I go ahead with the install. Is everything going to break? I'm so scared!
Be ready for the unexpected. You have several applications running in that server.
And see MSDN about that
Can anyone know why WIX Customaction.dll not working with Windows XP with service pack 3?As i developed my .msi with Wix setup in Windows 8 machine with VS 2010 environment.And this is working fine and is calling my customaction.CA.dll.Where as when i tried to test the same msi in windows XP machine this not working? do i need to do any changes in the customAction.dll so that it will work in XP machine also?Please help me to solve this issue.
Thanks
You might be used .NET Framework 4.0 (CLR 4.0) in your custom action. It will not run in .NET Framework 4.0 or newer is not installed machine.
In your XP machine .NET Framework 4.0 may not be installed. So that you’re custom action is not running.
Use useLegacyV2RuntimeActivationPolicy property in your CustomAction.Config file and set all supported time version which you want to use (CLR 2.0 for .Net Framework 2.0 and 3.5, CLR 4.0 for .Net Framework 4.0 and 4.5)
Assuming a WinPE 4.0 image is setup correctly with the WinPE-NetFx4.cab, WinPE-NetFx4_en-us.cab and prerequisite packages like WMI, should an app built in Visual Studio 2008 for .NET 3.5 execute? Or, is the app linked to strong name signed 3.5 assemblies such that it will not use the equivalent ones in .NET 4.0?
I'm also using WinPE 4.0 and experienced the same issue. Most of my app developed using earlier version of .NET Framework (.NET 3.0 & 3.5) will not execute (execute but nothing show up on screen)
A further investigation was made into the WinPE 4.0 WIM's Windows directory "Windows\Microsoft.NET\Framework" show only signs of version 4 (for my case v4.0.30319) was installed (WinPE-NetFx4.cab).
This concludes Microsoft's WinPE 4.0 only supports .NET Framework 4.
In order to make your app work again, re-compiled them using .NET Framework 4 assemblies.
I found that links:
Microsoft .NET Framework 4 (Web Installer)
Microsoft .NET Framework 4 (Standalone Installer)
Microsoft .NET Framework 4 Client Profile (Standalone Installer)
Note that (2) the size is 48.0 MB and the (3) the size is 41.0 MB. It's not the REAL .Net 4 Full Standalone. :(
I want that installer in a usb pen drive because my app need of features of .Net 4 Full Framework (like MSBuild) and I will install in a enviroment without Internet access.
PS: I tested the (2) and really is the Client Profile with another name... :(
Actually, you already found the full .NET 4 SDK. Microsoft put in a lot of effort to decrease the size.
The Microsoft .NET Framework 4
redistributable package installs the
.NET Framework runtime and associated
files that are required to run and
develop applications to target the
.NET Framework 4.
Have a look at this hanselpost.
The prerequisites have changed since .NET 3.5 SP1, .NET 4.0 requires at least XP SP3, Windows 2003 SP2 or Vista SP1. .NET 3.5 could be installed on any version of these operating systems, including a 11 year old completely unpatched version of XP.
So the 3.5 installer also needs to be able to update a bunch of native Windows components.
Not having to include the Windows component updates and additions allowed for a significant size reduction. If that's an issue then you'll have to include the Windows service pack installers on your pen drive.