.net 3.5SP1 on .net 3.0 server - Can I use the / bin folder in ASP.net?
One of my websites is on a shared hosting provider running either .net 2.0 or .net 3.0 but not 3.5 SP1.
I wonder if 3.5 SP1 can still be used by simply expanding all 3.5 assemblies into the / bin Folder, since technically it's still 2.0 CLR.
I know that if my host is ever updated, I have to delete them, otherwise a strange thing might happen and that I am driving to Unsupported-Territory at full speed, but is there a really big road sign that says DON'T DO THIS IS!" or even "This is not possible because of X"?
The main reason is that I want to use ASP.net MVC and possibly ADO.net Entity Framework, but I don't want to contract with another hosting provider.
Thank!
source to share
I'm sure you can't do this, but searching the following blogs might give you the definitive answer:
There will be problems, I think:
You want to load the system.dll file. Where does it look like? Does the PAC do precision? (I think it does) so you get 2.0. So you have system.dll v2.0 and you are trying to use a DLL (like system.web.mvc) linked to system.dll v3.5, but only in you / bin .... it should explode loudly without having the same contracts, etc.
Personally, I wouldn't try, especially in production. But if you can take a seat for a while, let it go. In the worst case, you need to delete the files and re-upload the old site.
YMMV :)
source to share
In theory this can be achieved, but it is definitely not recommended.
Scott Hanselman made a post on how to run ASP.NET MVC on a server with a different .NET 2.0 installed, see http://www.hanselman.com/blog/DeployingASPNETMVCOnASPNET20.aspxThis is a very important post "works on my machine".
All DLLs in an ASP.NET site can be inside / bin if they are specified correctly. My suggestion is to create a virtual machine (MS Virtual PC - free), install only .NET 2.0 / .NET 3.0, and then copy the desired DLL from the .NET 3.5 installation (hint - you will find the DLL in% Program Files% \ Reference Assemblies).
I am not responsible for the damage caused to your provider from this answer
source to share
I have successfully executed some EntityFramework sites on hosts that only had .net 3.5 installed. I copied System.Data.Entity.dll and System.Web.Entity from Program Files% / Reference Assemblies. I also had to change my web.config and remove references to System.Data.Entity and System.Web.Entity.
Update: This method will not work for DynamicData or EntityDataSource web element. I believe it is related to System.Web.WebExtensions.dll which already exists in the GAC from 3.5
source to share