[dba-VB] c# - Creating and using a shared module

jwcolby jwcolby at colbyconsulting.com
Fri Mar 11 21:09:49 CST 2011


I found a "make project from existing files.  When I did that it offered to use a selected directory 
so I dragged the project directory into a new directory and told it to use that.  I selected a class 
library type of project and it went to work "converting" my existing project into a class library.

112 compile errors, most having to do with the fact that it no longer understands

using System.Windows.XYZ

Many of the common classes did things like accept a combo loaded data into it in a standard way. 
Stuff like that.

So there we are.

I "just did it"!  ;)

John W. Colby
www.ColbyConsulting.com

On 3/11/2011 9:37 PM, jwcolby wrote:
> You make it sound so easy, but it is an existing project already which was not created as a class
> library project. I need to create the class library project then somehow get the directories and
> files into that project and get it to compile.
>
> At that point I can reference it by other solutions.
>
> John W. Colby
> www.ColbyConsulting.com
>
> On 3/11/2011 12:52 PM, Shamil Salakhetdinov wrote:
>> Hi John --
>>
>> <<<
>> Any suggestions, tips and tricks, warnings, how to etc.?
>>>>>
>> Just do it! :)
>>
>> I mean if you managed to handle MS Access library databases then handling
>> .NET class libraries would be a "breeze" work for you.
>>
>> Create class library project - you can keep it within its own solution
>> having main (console) project of that solution as a (unit) test one.
>> Put all three solutions - two application ones and class library one in
>> subfolders of the same root folder. (You can do it differently but this is
>> how it's done usually AFAIK)
>> Add existing class library project to application solutions.
>> Reference class library projects from application projects.
>> if you use VS2008 and you have a good PC with plenty of memory (and you have
>> one don't you?) then you can keep all three solutions open in three
>> instances of VS2008.
>> Just keep tack from which solution you have made class library code changes
>> last time - when you'll switch to the other solution and if you have the
>> same source code file opened in it you'll get a message like that "Source
>> file changed - would you like to reload it?" - reply yes...
>>
>> ...
>>
>> Use SVN or Mercurial for source code control. Do commit source code changes
>> to the source code repository from time to time...
>> ...
>>
>> I have 58 projects in one of the solutions here - that results in more than
>> 5 apps and quite some class libs compiled and built - AFAIK folks do have
>> more than hundred projects within solutions sometimes...
>>
>>
>> Thank you.
>>
>> --
>> Shamil



More information about the dba-VB mailing list