Sharing common code

From: Jeffrey Bradshaw (Jeffrey.Bradshaw_at_Dictaphone.comNOSPAM)
Date: 02/11/04 

Date: Wed, 11 Feb 2004 09:33:49 -0500

I have two apps (one is a service and one is a windows app) that share some
common classes. How can I make it so that I don't have to keep updating the
items in solution explorer?

Here's what I do now:
Test and debug the windows app. Make appropriate changes required there.
Once it's to my liking, I open the service app solution, tell it to add an
existing item and go and get the item from the windows app. It then copies
the file in to the service directly. Ideally I'd like to leave the code in
some common place that everybody can reference.

I've thought about making a DLL out the common class but 1) Don't know how
to do that and 2) how do you debug a dll?

TIA - Jeffrey.

Relevant Pages

  • Custom classes with web services
    ... I also have a Windows app that will reference a couple of web services. ... Each web service references the .dll to get the user class. ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • Re: Keeping objects between requests within the same session
    ... I tried using that, but when working with my Windows App accessing the DLL, ... to initialize it, so to speak (I imagine this is explicitly doing what, in a ... > the current page request. ...
    (microsoft.public.dotnet.framework.aspnet)
  • TCP Address Question
    ... I have an ASP.net page that uses a dll to send a request via TCP ... The Windows app receives (TCPListener / TCPClient / XMLDeserialiser) ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Sharing common code
    ... > I have two apps (one is a service and one is a windows app) that share some ... > common classes. ... > I've thought about making a DLL out the common class but 1) Don't know how ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Getting Appropriate Context????????????????
    ... If System.Web.HttpContext.Current is null, then its a windows app, otherwise ... > I m working on a DLL that can be used by both the web based clients (like ... > all the intrinsic objects. ... > Remember the old days of getting web context in our VB/VC dll through some ...
    (microsoft.public.dotnet.framework.aspnet.security)