Sky Software Homepage LogicNP Software Knowledge Base And FAQ

 
Contact Product Support    SearchSearch      Subscribe to the RSS feed for this forum

INFO : Deploying EZNamespaceExtensions.Net on computers with multiple versions of the .Net runtime installed.

 
Subscribe to the RSS feed for this forum  Forum Index -> EZNamespaceExtensions.Net
View previous topic :: View next topic  
Author Message
Support



Joined: 18 Jul 2005
Posts: 731

Posted: Sat Feb 03, 2007 4:39 am    Post subject: INFO : Deploying EZNamespaceExtensions.Net on computers with multiple versions of the .Net runtime installed.

Namespace extensions may be loaded by arbitrary processes and before .Net runtime v4.0, managed code built against one version of the .Net runtime could not run in a process which has already loaded another version of the runtime.

The latest .Net 4.0/VS 2010 runtime fully supports in-process side-by-side loading of the .Net 4.0 runtime (and ALL future runtimes) with earlier .Net runtimes. See following excerpt from
http://msdn.microsoft.com/en-us/magazine/ee819091.aspx
"With the ability to have multiple runtimes in process with any other runtime, we can now offer general support for writing managed shell extensions-even those that run in-process with arbitrary applications on the machine."

Even if you develop your namespace extension using .Net 3.5 or earlier (VS 2008 or earlier), this is only a issue if your namespace extension will be distributed to the general public. This is not an issue at all if your namespace extension is going to be deployed internally within your company or in a similar controlled environment (as is often the case with namespace extensions). In this case since you know which versions of the .Net runtime are going to be installed on your company's computers you can use the corresponding tool for development. For example, if your company's computers will have .Net 2.0 runtime installed then you can safely develop your namespace extension with Visual Studio 2005. If your company's computers have only the .Net 1.0/1.1 runtime installed, then you should use VS 2002/VS 2003 or you can even use Visual Studio 2005 while targeting the 1.0/1.1 runtime when compiling (using MSBuild or various widely available setting files).

Even if your namespace extension is going to be available to the general public, the solution is to target the 1.0/1.1 runtime, so that no matter what .Net runtime is installed on the user's computer, it will always be able to load your namespace extension.
Back to top
Display posts from previous:   
Forum Index -> EZNamespaceExtensions.Net All times are GMT
Page 1 of 1

 
Jump to:  


Powered by phpBB © 2001, 2005 phpBB Group