When you build a .NET Framework application against a specific version of a strong-named assembly, the application uses that version of the assembly at run time. However, sometimes you might want the application to run against a newer version of an assembly. An application configuration file, machine configuration file, or a publisher policy file can redirect one version of an assembly to another.
more details are here http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconassemblyversionredirection.asp
With Best Regards,
Mitesh Mehta
Email : miteshvmehta@gmail.com
http://cc.1asphost.com/miteshvmehta/
Saturday, October 23, 2004
Application Restore Utility
In v1.0/v1.1 of the CLR, there is a relatively obscure feature known as the .NET application restore tool. This feature makes use of log files which record binding information when running a managed app. The idea is that if binding policy for your application changed, the tool would be able to analyze this data, and generate an app.exe.config file, which can get you back to binding settings you used previously.
To know more about .NET Application Restore Tool navigate to http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconusingnetapplicationrestoretool.asp
With Best Regards,
Mitesh Mehta
Email : miteshvmehta@gmail.com
http://cc.1asphost.com/miteshvmehta/
To know more about .NET Application Restore Tool navigate to http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconusingnetapplicationrestoretool.asp
With Best Regards,
Mitesh Mehta
Email : miteshvmehta@gmail.com
http://cc.1asphost.com/miteshvmehta/
Activator.CreateInstance() Method
Activator is a class in System namespace...
This class is one of the most widely used class to create instances at runtime, of types locally or remotely defined...
Usually it returns back an object or an objecthandle...
There are lots of overloads of this method and in local scenarios mostly take System.Type() as one of the parameter...
Its certain overloads also take typename as string and return back an object handle...
This objecthandle then needs to be unwrapped to get back the object...
The overload which returns objecthandle is mostly used in Remoting...
CreateInstance is a static member of the class and so can be accessed directly without object creation...
With Best Regards,
Mitesh Mehta
Email : miteshvmehta@gmail.com
http://cc.1asphost.com/miteshvmehta/
This class is one of the most widely used class to create instances at runtime, of types locally or remotely defined...
Usually it returns back an object or an objecthandle...
There are lots of overloads of this method and in local scenarios mostly take System.Type() as one of the parameter...
Its certain overloads also take typename as string and return back an object handle...
This objecthandle then needs to be unwrapped to get back the object...
The overload which returns objecthandle is mostly used in Remoting...
CreateInstance is a static member of the class and so can be accessed directly without object creation...
With Best Regards,
Mitesh Mehta
Email : miteshvmehta@gmail.com
http://cc.1asphost.com/miteshvmehta/
Build Vs Rebuild in VS.Net
A very basic but a less know question for today...
What is the difference between Build and Rebuild solution in VS.Net or why at all we have two...
Well the difference is that Build solution will build only those projects which are changed since the last build... It will not get the changes of the updated embedded resource files...
Rebuild soultion will cause everything to be rebuilt no matter whether it was changed or not...
If you are making small projects the differences would not matter much but for large builds these are really useful...
There are advanced differences though but these are something which all should know...
With Best Regards,
Mitesh Mehta
Email : miteshvmehta@gmail.com
http://cc.1asphost.com/miteshvmehta/
What is the difference between Build and Rebuild solution in VS.Net or why at all we have two...
Well the difference is that Build solution will build only those projects which are changed since the last build... It will not get the changes of the updated embedded resource files...
Rebuild soultion will cause everything to be rebuilt no matter whether it was changed or not...
If you are making small projects the differences would not matter much but for large builds these are really useful...
There are advanced differences though but these are something which all should know...
With Best Regards,
Mitesh Mehta
Email : miteshvmehta@gmail.com
http://cc.1asphost.com/miteshvmehta/
Subscribe to:
Posts (Atom)