Wrox Programmer Forums
Go Back   Wrox Programmer Forums > .NET > .NET 1.0 and Visual Studio.NET > VS.NET 2002/2003
|
VS.NET 2002/2003 Discussions about the Visual Studio.NET programming environment, the 2002 (1.0) and 2003 (1.1). ** Please don't post code questions here ** For issues specific to a particular language in .NET, please see the other forum categories.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the VS.NET 2002/2003 section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old March 10th, 2005, 02:08 PM
Registered User
 
Join Date: Feb 2005
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default 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





Similar Threads
Thread Thread Starter Forum Replies Last Post
modifications in legacy application menus ayazhoda Access VBA 2 May 7th, 2008 05:14 AM
References and VB ’05 Web Project BrianWren Visual Basic 2005 Basics 0 December 15th, 2006 04:23 PM
Need of struts-legacy.jar sam123 Struts 1 May 24th, 2006 10:24 PM
Addin Project References bdancis Excel VBA 1 February 10th, 2005 08:11 PM
Adding Web References to a project.... vb_developer C# 0 September 5th, 2004 01:32 AM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.