Hi Bonnie

That makes sense. I just have to start thinking about where to draw the lines to define the projects.

Thanks,
Simon White

>Simon,
>
>Oh, definitely you need to have multiple DLLs. Each project compiles to a DLL. Our projects basically reflect app functionality. For the UI stuff, we'll have separate projects for Personnel, Inspection and Activity modules (for example), with corresponding separate projects for Business classes (broken down the same way, Personnel, Inspection and Activity) and separate projects for DataAccess classes. Also, a separate project for BaseClass UI controls (textbox, combobox, etc ... these are basically all in one project).
>
>Hope this gets you started.
>
>~~Bonnie
>
>
>
>>Hi Bonnie
>>
>>In order to assure the dlls are downloaded quickly I assume it would also be good to insure that that application consists of multiple dlls instead of one monolithic one. If I remember correctly from my experimenting with VS.Net in 1.1 it compiled my project (at least the classes I created) into a single dll. This could be a problem if the application is large. Any suggestions on reasonably ways to breakdown the project into several smaller dlls?
>>
>>I am beginning to think that this capablity might be enough to start me moving in the .Net direction.
>>
>>Thanks,
>>Simon
>>
>>
>>
>>
>>>Simon,
>>>
>>>You didn't say if you were using 1.1 or 2.0. We've done this sort of thing with 1.1 and, as Kevin mentioned, 2.0 has made it easier with "ClickOnce" (although I haven't tried it yet).
>>>
>>>If you *are* using 1.1, then Search MSDN for "Smart Client", or try this link: http://msdn.microsoft.com/netframework/programming/winforms/smartclient.aspx
>>>
>>>Here's the details in a nutshell:
>>>
>>>Basically, you simply need to use the Assembly.LoadFrom method from the System.Reflection class to load your DLLs. It's as simple as that.
>>>
>>>Ideally, you should architect your application so that there is a small, lightweight executable installed on the client machine. This executable need not contain much in the way of core logic. Ideally, it just references the DLLs it needs, which reside out on a remote Web server and which supply all of the necessary application logic. We use a Outlook-style sidebar to launch all our modules and they are all loaded through Reflection.
>>>
>>>The first time a particular assembly is referenced, it is downloaded to the assembly download cache on the client computer and loaded for use. Going forward, if the assembly required is already on the client computer and the version on the Web server has not changed, the local copy will be loaded. If the version on the Web server has been updated, that new version will be downloaded and executed. Thus, updates are automatically propagated to the client, but the network is not flooded with redundant downloads.
>>>
>>>If you haven't architected your application that way to begin with, you could add something to your app to do it after the fact (how you implement this is up to you ... you could have a special form that requires the user to start the download process, or you could do it automatically every time you start the app (could take awhile, depending on how many DLLs you have). But, anyway, here's basically all you need:
>>>
>>>

>>>// First, an ArrayList containing the filename of all your DLLs.
>>>// This can be a class, as shown below, or simply a property
>>>public class AssembliesList : ArrayList
>>>{
>>>	public AssembliesList()
>>>	{
>>>		this.Add("MyMainControl.DLL");
>>>		this.Add("MyBusiness.DLL");
>>>		this.Add("SomeOtherOnes.DLL");
>>>	}
>>>}
>>>

>>>

>>>// Next, the method that actually does the work:
>>>private void DownloadAssemblies()
>>>{
>>>	string URL = GetTheURLWhereYourAssembliesAreLocated();
>>>	string DLL;
>>>	AssembliesList oList = new AssembliesList();
>>>
>>>	for (int i = 0; i < oList.Count; i++)
>>>	{
>>>		DLL = oList[i].ToString().Trim();
>>>		try
>>>		{
>>>			System.Reflection.Assembly o =
>>>				System.Reflection.Assembly.LoadFrom(URL + DLL);
>>>		}
>>>		catch (System.Exception ex)
>>>		{
>>>			MessageBox.Show(ex.Message);
>>>		}
>>>	}
>>>}
>>>

>>>
>>>~~Bonnie
>>>
>>>>Hi Kevin
>>>>
>>>>I have been trying to read as much as I kind find but have yet to actually see a real life demo.
>>>>
>>>>Thanks,
>>>>Simon
>>>>
>>>>>Simon,
>>>>>
>>>>>I can give you some information, but to start with....have you looked at the new ClickOnce deployment capabilities using VS2005?
>>>>>
>>>>>Kevin