This blog is about developing Windows applications using Visual Studio. All postings on this weblog are provided "AS IS" with no warranties, and confer no rights. Use of any samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
Your host Nikola Dudar is a Program Manager in Windows division of Microsoft Corporation. He has been working on Windows Web Services API during Windows 7 and various additions to Visual C++ during VS2005 and VS2008. More details are in LinkedIn profile under Nikola's formal name Mykola Dudar.
If you are interested in program management and project management, check out my other blog at http://www.pmsnack.com/ where I collect best practices and other topics interesting to program and project managers.
To send feedback, comments or requests for new posts, please use the contact form.
This came up one more time today, so I have decide to blog two links to well-done KB articles.
1) Applications that bypass globally serviced side-by-side assemblies may be vulnerable to issues that are fixed by a Microsoft software update - recommendation learned in hard way
2) GDI+ 1.0 Security Update Overview - a hard lesson
Long story short, several recommendation that were learned from mistakes made by others, you may find usefull for you:
- ship your applications with manifest that enumerates sxs assemblies used in this application
- always deploy manifest for SxS assemblies, even if you deploy applocal.
- If OS already installs this assemblies in WinSxS, do not install them applocal
- DLL/COM redirection is a nice feature, but do you really want to use it?
- Do not explicitely specify path to a library in LoadLibrary() call.
- Use <publisherPolicy apply="no"/> with caution.
Go ahead and read these articles. MSDN also has many pages on isolated applications, side-by-side assemblies.