Legacy references in a duplicate project
I am SO close to finishing a project based on ThePhile, but I'm having trouble with two things that are unrelated except that the first makes the second difficult. I am sure they are things related to VS (2003) rather than ThePhile, but I'm having a hard time finding this particular bit of information at Microsoft so I thought I'd try here...
First, during the development on my project based on ThePhile, Visual Studio began to quit -- without any error messages -- whenever I try to create a new project, form, library etc. I CAN create a new folder or a new blank solution. I've checked my permissions on IIS, and I've even re-installed VS. Does this sound like a VS problem, an IIS problem, or something else? Any ideas to try?
Second, I'm trying to create two modules based on the NewsManager. (The original NewsManger project was renamed "Providers") and modified. Since I can't start with a new project, I tried to duplicate the completed "Providers" module on my disk and gave them new names. I can get everything imported into the solution ok, and have changed all the namespaces, etc., but when I try to set references to "Sales.Business", "Sales.Configuration", and "Sales.Data", VS thinks I'm pointing to the original set called "Providers.Business", "Providers.Configuration", and "Providers.Data". The references simply get relabeled (e.g., a reference to "Providers.Business" in a project changes to "Sales.Business" or vice-versa, but the path to the file (and it's properties) clearly point to the original "Providers" assemblies in both cases. What do I need to change to ensure the references to "Sales.x" go to the proper assemblies?
I'm sure there must be simple, well-documented answers somewhere, but I am at a loss to find them... I've posted at Microsoft, but have had better luck finding answers here... Any help would be much appreciated. Not sure where to find this information.
Thanks!
John
|