Griffiths, Richard
R.Griffiths at bury.gov.uk
Fri Jul 22 11:09:18 CDT 2005
Hi I think if you add the project (which contains the code in the dll) to your solution you can then debug the dll code - you can then set a reference in your main project/solution to reference that project (as opposed to the dll) HTH Richard -----Original Message----- From: dba-vb-bounces at databaseadvisors.com [mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of John W. Colby Sent: 22 July 2005 16:24 To: dba-vb at databaseadvisors.com Subject: [dba-VB] Add executable solution to project I am working on a set of classes in a project which need Imports System.Data.OleDb Imports System.Data Imports System.Collections I was developing them in a class library, and all is cool. However I can't just throw a form in there and run the thing to test it, I get a "cannot be started directly" error. So... I tried just copying the classes (all in one module, THAT is cool) into a window project. Of course(?) now the imports don't work. Sigh. So I created a Window project and referenced the dll from my class library. That is cool as well, however... I really want to interactively debug the class library. The error message when trying to run the class library code (directly) says to "add an executable project to this solution which references the library project". I can't seem to find any way to directly add my window project (which references the class library) to the class library solution. Anybody know how to do this? This BTW is exactly why I have never gotten anywhere with .net so far. I promptly get bogged down in details with no readily available help. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ _______________________________________________ dba-VB mailing list dba-VB at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-vb http://www.databaseadvisors.com