Jump to content
Sign in to follow this  
Pat Foley

Question about Guid in dproj

Recommended Posts

The dproj has a Guid assigned to it.  It rhymes with Gui-de cheese most of the time. but when it used as interface* that once named can't be changed or need to be renamed if the Interface* is changed. If not then Guid rhymes with Squid.

 

The question is when the project is not compiling--OK to just index the Projects Guid until the bad code is removed or repaired? I bumped the projects Guid 3 times to fix a boo-boo. But likely not a good practice to share.

         

Or say some naive person like me lays out a blank project with its directory and sub directories laid out, then copies the layout to new directory for a new project, finds out later there's two projects with same Guid.

*If is used as an Interface not just a marker.

 

Pat

Note seen an eye catcher at line 4689 in System.Classes Putting 4690 first would read better     

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×