Which is the best way to deploy an asp .net 3.5 project?
I have a production server with IIS 6.0 on Windows Server 2003. I found that there are several to deploy it, but I think that xcopy deployment is OK for now.
However, I don't found the right to do it. Some tutorials suggest to create virtual directories, but I don't know where is the target
There's more information you need than can be put in a simple answer, and this is borderline off-topic.
However, I do have a link for where you should start: Deploying ASP.NET Applications in IIS 6.0 (IIS 6.0)
It's an older series of articles, but still applies.
Related
I would like to be able to run my published site on my arvixe shared hosting (if it's possible now, as it's only beta4 now), and on my dev machine's IIS 8.5.
It's a dnx-clr-x64.1.0.0-beta4 ASP.NET 5 project. (dnx451) I'm thinking of using the full .NET, not the Core. It would be also nice, NOT to publish the source code.
I'm using Visual Studio Community 2015 RC.
Can it be done, and can it be done from VS, without console commands?
Thanks.
Is it possible to host a .NET 4 application under a .NET 2 site?
For several reasons we have to run the main site on .NET 3.5, but there is an application written in entity framework 4, which hosted under the same domain/port.
When I try to add an application under the site (using a different .net 4.0 application pool), i get an error stating duplicate content in web.config. I have searched the net for fixes, but none of them seems to be working for me.
I am running a Windows Server 2008 R2 with IIS7.5
Any help would be appreciated.
It is possible to fix, if you carefully read Microsoft's document,
http://msdn.microsoft.com/en-us/library/a99txfy5.aspx
and
http://www.asp.net/whitepapers/aspnet4/breaking-changes#0.1__Toc256770150
No, that's not possible. An assembly compiled against .NET 4.0 must be run inside CLR 4.0. It is possible the other way around: run an assembly compiled against .NET 2.0 inside CLR 4.0.
No, the nested application will not be able to set a seperate framework version. I would suggest changing the version on the main site to v4. I don't think you should experience problems running a 3.5 app on version 4. What are your reasons for running it in 3.5?
I am very new in IIS 7.0 (Using in Windows Server 2008).
I have my Web application developed in VS 2005 or ASP.Net 2.0. in Windows Server 2003 system.
Now i am migrating to Windows server 2008 + IIS 7.0, So please can any tell me what are the basic setting i have to perform on IIS 7.0 to run my existing application without any changes in code.
I read somewhere that i have to change my Web.config file.
Dont worry my friend, i just follow the following simple steps and it works for me
1- i copy the folder containing the application into the www root folder
2- open IIS from RUN INETMGR and check the application pool: make sure it contains .NET 2
3-convert to application
4-choose the classic .NET v2
5- set permissions and run the application
Good Luck !
This is a very useful link
ASP.NET 2.0 Breaking Changes on IIS 7.0
if you face any trouble, send your problem as comment and i will answer it
You may want to change your application to classic mode instead of Integrated mode, there are some gotchas moving into integrated mode. Its something to consider at least. Hopefully you have the opportunity to test before going live with IIS 7.
I'm moving an ASP.NET project from .NET 3.5 to .NET 4.
Everything works beautifully if I'm debugging under web.dev (ie. in Visual Studio [2010]) but as soon as I try and run this under IIS7[.5] the debugger fails to attach. Running the project directly under IIS just causes it to throw back 403s (no subcode, so not much help there).
I setup the site by taking the current (and working!) .NET 3.5 site, and changing the AppPool to one with the .NET 4 runtime. I've confirmed that all file permissions are kosher (at least from the .NET 3.5 perspective). I feel as though I'm missing some configuration step here...
The error message when trying to attach the debugger is just "Unable to start debugging on the webserver." Not the most useful error message in the world.
Directly attaching to the associated w3wp process strongly suggests that the application is never spun up successfully.
The basic question is, how would I affect this change over from .NET 3.5 to .NET 4 for a project running under IIS?
Figured it out.
.NET 4 had not been installed for IIS purposes. Don't ask me why that was the case.
Running asp_net_regiis -i in the .NET 4 install directory (\Windows\Frameworks\v4.0.xxxx) under the Visual Studio Command Prompt (x64 in my case) solved the problem.
You cannot mix .NET frameworks in the same app pool. So ensure that only .NET 4.0 web sites are in your app pool.
Remember to set the web site/virtual directory to .NET 4 as well.
IIS7 has two options within a "website". In IIS6 you'd add a sub-app as a "Add Virtual Directory..." in IIS7 doing so forces you to keep the same AppPool and thus .NET framework version as the website.
But, IIS7 now has an "Add Application..." options, which allows you to essentially do what IIS6 had allowed, so that you can explicitly state the AppPool to run in and it can differ from the parent website.
Start a fresh project from scratch and just use the web.config there. Copy all your 3.5 pages in there and manually move over web.config elements that you need. The pages themselves don't require any converting, it's all in the web.config. The web.config for a .net 4.0 page is actually significantly smaller due to the fact that .net 4.0 is not just an extension of .net 2.0 like 3.5 is.
I just got application written in ASP.NET and VB, can i deploy it on any IIS?
Are there any files in project with that kind of information?
There are no files or magic numbers anywhere that can tell you this. Chances are preety good that it will run on a newer versions of IIS but even then your goign to need to know what functionality it requires. For example is it using WebDav? IIS is preety good at being backwards compatible but forward compability not so good. For example IIS7 introduced new functionality which if the application is using it, would prevent it from running on IIS6.
Do you know what version of .net it requires that is more likely to bite you then anything else?
Any IIS that supports ISAPI, I guess, but IIS 5.1 + is recommended (.NET probably won't run on OS that run IIS4 anyway).
Here is a good MSDN link detailing which IIS version comes with which version of Windows as well as useful links for configuring it.
ASP.NET and IIS Configuration
IIS 6 is the minimum for recent .NET versions (i.e. Windows 2003) because Win2000 is not supported (considering server only here).
The Windows version will tell you the IIS version:
Server 2003: IIS 6
Server 2008: IIS 7
Server 2008 R2: IIS 7.5
Also XP: IIS5.1; Vista: IIS7