Subscribe: .Text Blog
Added By: Feedage Forager Feedage Grade C rated
Language: English
blog  code  created  decided  file  new project  new  opened  project file  project  sense  studio  text  visual studio  visual  world 
Rate this Feed
Rate this feedRate this feedRate this feedRate this feedRate this feed
Rate this feed 1 starRate this feed 2 starRate this feed 3 starRate this feed 4 starRate this feed 5 star

Comments (0)

Feed Details and Statistics Feed Statistics
Preview: .Text Blog

.Text Blog

Another .Text Powered Blog

Copyright: Blog Author

My first blog entry

Thu, 29 Jul 2004 16:15:00 GMT

Originally posted on:

Well today has been starting off pretty good.  Yesterday I created a pure mess in one of my visual studio solutions.  I had four projects that i was trying to combine into one project, so through the code into the one project no problem right.  I got everything to build and all was good in the world.  Well me being the structured clean freak I was.  I decided to copy the project into a appropriate folder that made more sense.  (outside of Visual Studio).  Well this were things get sour I opened up my solution and decided you know what it makes sense to keep one class in its own assembly, It just so happened to be the original project that i had copied. so i figured OK this should be easy.  Sure enough everything built fine, but when you try at add a project reference to another project.  it keeps selecting the wrong project.  After about an hour of pulling my hair out.  i decided to open up the project file in an XML editor, and sure enough i found my answer. I noticed a unique GUID and when i opened up the old project file and the new project file the GUID's were the same.  Well instead of messing with the internal workings I copied out my source code and created a brand new project, now everything is truly happy in the world. :)  The morale of this story is to always create a new project never try copying and reuse an existing one. (image)