Hi I have an application which has a main project set to ver 3.5 with some utility projects set to ver 2.0. I need to migrate the app to work on IIS7.5. I have tried recompiling the app as is and putting it on the server but to no avail.
What do I need to do to get this app running on 7.5? Will I need to upgrade the projects in the solution to .net 4.0?
any pointers much appreciated.
No you don't necessary need to upgrade to .NET 4.0 even if it could be nice :-) All you need is to make sure the application pool is set to use CLR 2.0 in IIS and it will run just fine (obviously .NET 3.5 needs to be installed on the server).
Related
I am pretty new to asp.net mvc development. I have developed an asp.net mvc4 app targeting .NET 4.0 and using EF 5.0 for database connection. Now I want to deploy this app in a Windows 2008 server with IIS 7.5. What are the things I need to make sure that are installed in the server for this application to work properly?
Thanks!
Only two: .NET 4.0 and optionally MVC 4. You can avoid installing MVC 4 if you include binaries in your deployment package.
EF5 you standard .NET 4.0 and for sure you have reference to it, so all needed binaries will be in deployment package
Download MS Web Platform Installer 4.6 if you haven't already on the new Windows 2008 server.
http://www.microsoft.com/web/downloads/platform.aspx
Search for 'Recommended' in the top right search box.
Select and install 'Recommended Server Configuration for Hosting Providers'.
This will install all SQL drivers etc (probably too much in fairness, but in fewer steps) that you need to run .net 4.5 apps, and make it possible to deploy using Web Deploy.
The details of the process can be found in this article
http://www.orcsweb.com/blog/gabe/how-to-install-webdeploy-on-windows-server-2012/
I have a documentum 5.3 SP3 content server installed on a machine And one .net application is also installed on the same machine
current .NET version is 2.0
and i want to install the .NET version 4.0 on that machine.
So, I want to know if that install will in any way interfere with
Documentum?
You can install different versions of .Net frameworks on a machine and everything should work fine. The documentum content server does not need .Net framework installed. So I suppose you are using something 3rd party/homebrew component, maybe you should ask the developers of that stuff.
You can install all major versions of .Net concurrently, so there should be no issue. This is completely independent of Documentum.
I've got an old Windows 2003 server running IIS 6, and I chose .net 4.5 for my latest web app. Problem is I can't get it to run on the server...
.NET 4.0 framework is installed. I've run aspnet_regiis and deployed the website. I gave it it's own application pool. But I'm getting the following error:
The 'targetFramework' attribute in the <compilation> element of the Web.config
file is used only to target version 4.0 and later of the .NET Framework (for
example, '<compilation targetFramework="4.0">'). The 'targetFramework' attribute
currently references a version that is later than the installed version of the
.NET Framework. Specify a valid target version of the .NET Framework, or install
the required version of the .NET Framework.
I saw the requirements for .NET 4.5 as requiring Windows Server 2008 or later, but I'm seeing lots of posts with people just needing to configure the routing for MVC4 so it seems like this should be possible.
So any ideas what I need to do in order for this to work?
EDIT: The strange thing is we are using an ASP.NET Web API site that works just fine... but that should require .net 4.5...
.Net 4.5 cannot be installed on Windows Server 2003.
Instead, you should use MVC 4.0 on .Net 4.0, which will work fine.
I've just downloaded and installed Visual Studio 11 Beta. I looks great and I was thinking about upgrading some of my website to ASP.NET MVC 4 and .NET 4.5. The question I have is if I can run such a website on a hosting plan that has only .NET 4 installed? Maybe by marking the necessary dependencies as "copy local"? I've search around, but as this beta is fresh from the oven, I couldn't find any helpful data.
I think you should have problems with your hosting. Anyway as many will say using beta for production is not a good idea (although I had done it several times). My suggestion is to switch to some HyperV hosting and install all necessary frameworks there.
i had similar problem,i have visual studio 2012 and my host running for .net 4.0
but my site was .net 4.5
when uploaded and saw the site i got error.
i backed up program.
then went to
C:\Program Files\Reference Assemblies\Microsoft\Framework\.NETFramework
there were 3 folder v3.5 v4.0 v4.5
then i created 2 back up folder one for 4.0 and other for 4.5
from each v4.0 and v4.5 copy these:
1-System.ComponentModel.DataAnnotations.dll
2-System.ComponentModel.DataAnnotations.xml
3-System.Data.Linq.dll
4-System.Data.Linq.xml
now that i had back ups did these:
1-change target framework to 4.0 from project options
2-copied above assemblies from folder v4.5 to v4.0
then build application
everything went well.
good luck.
Presently .Net 4.0 is not supported on Azure.
This thread indicates that you will not be able to use .Net 4.0 with VS 2010 until it is supported in the cloud.
http://social.msdn.microsoft.com
I'd like a way to start developing Azure applications locally utilizing the new features of .Net 4.0. I am fine with not being able to deploy these applications until Azure officially supports it.
From within the VS IDE; I tried replacing .Net 3.5 application references with newer .Net 4.0 references and Visual Studio crashes.
Does anyone have any suggestions?
Thanks,
Paul
An update to this old thread. .Net 4.0 has been supported since Azure SDK 1.2
Some features from .NET 4.0 can be added to your application through other means. For example, the recently-released Reactive Extensions for .NET 3.5 SP1 includes a back ported release of Parallel Extensions. And the Managed Extensibility Framework contains the Lazy class and Tuple struct. As long as you set "Copy Local" to true on any libraries that you add, your application should run (and deploy) successfully.
Obviously, these aren't all the features that are new in .NET 4.0, and not all of them will can be ported back to .NET 3.5 like these can.