visual studio .net general: When i build a project that contains com objects VS starts the build by unregistering the objects

Is there any way to force VS to leave the script that it executes to unregister the objects around so that i can see what it is doing

The second issue concerns building .NET COM components. Each time VS begins a build it claims that it is unregistering the objects but a glance at the registry shows this to not be the case. .Net builds cause the version number to increment. Checking the registry shows that the is an entry for each execution of a the debug build. So far I am only able to remove these entries manually via regedit which is very painful. Can I force VS to really remove the prior entry or to always use the same version info

Than

Use a fixed version in AssemblyInfo.xx instead of 1.0.*. Use GuidAttribute
on your Class (and interface if you have one) so that VS stops providing one
for you. VS might well be unregistering the previous version of the current
one it's building, however it's always a new one, not the old one.
--
Phil Wilson
[MVP Windows Installer]
Definitive Guide to Windows Installer
http://apress.com/book/bookDisplay.html?bID=280

[quoted text, click to view]
begins a build it claims that it is unregistering the objects but a glance
at the registry shows this to not be the case. .Net builds cause the
version number to increment. Checking the registry shows that the is an
entry for each execution of a the debug build. So far I am only able to
remove these entries manually via regedit which is very painful. Can I
force VS to really remove the prior entry or to always use the same version
info?
[quoted text, click to view]