View Single Post
  #10  
Old 06-26-2007, 02:41 PM
smckeown smckeown is online now
Registered User
 
Join Date: 05-01-2007
Posts: 18
Thanks for the response. I really do appreciate the time and effort.

What I am really looking for the technical explanation for WHY the GUIDs do not match.

I was thinking not matching the GUIDs was a Visual Build Pro design decision (or bug) and was most likely based on some bit of Visual Basic or GUID magic that the designers know.

The purpose of my post is to gain technical insight as to WHY Visual Build Pro doesn’t sync the GUIDs. The project 'runs fine' seems a bit like when a programmer says “It runs fine on my machine” in response to a bug report. _grin_

For instance, perhaps the Visual Build Pro or folk or others know some low level internal VB GUID resolution magic.

Or, perhaps there are MSDN or MS posts about this that I haven’t been able to find. (A link would be great).

Or, perhaps Visual Build Pro folk ‘know’ that the GUIDs don’t have to match because “insert a learned Microsoft nugget of wisdom here.”

Thank again for any inputs…
-Sheryl
Reply With Quote