Hello Vlado,
If you are using Visual Studio 2005, having multiple projects in one solution
(even different languages!!) and referencing them is not at all a burden.
You can easily do that. Start with modularize your whole project into small
parts and utilities. If you can separate some components, move their coding
into seperate DLL file and provide wrapper if needed.
It should not be so hard.
=============
Regards,
Jigar Mehta
Vv> Hello Jigar,
Vv>
Vv> I understand that this change will have to involve more than simply
Vv> running some utility but we would need some directions as to how to
Vv> achieve it.
Vv>
Vv> We were looking at having multiple projects within one solution but
Vv> cross-referencing would be huge burden.
Vv>
Vv> Thank you for your input.
Vv>
[quoted text, click to view] Vv> "Jigar Mehta" <jigar.programmer@gmail.com> wrote in message
Vv> news:6bab533f0e698c8e1514686a649@msnews.microsoft.com...
Vv>
>> Hello Vlado,
>>
>> I think that will involve changes at architecture level. You will
>> have to design the application like that, your object modal will also
>> reflect that design. There is no inbuilt option that you can break an
>> EXE into multiple DLL files by using some utility !
>>
>> =============
>> Regards,
>> Jigar Mehta
>> Vv> Hello,
>> Vv> Vv> We're developing application in VS2005 using vb.net.
>> Vv> Vv> Our application exe file is ~20mb when compiled.
>> Vv> Recently, we have developed auto-update feature that goes on our
>> Vv> web-site,
>> Vv> authenticates through WebServices and if neccessary downloads
>> Vv> updated
>> Vv> app.exe file. We had to use custom solution vs. ClickOnce for
>> Vv> several
>> Vv> different reasons.
>> Vv> Now, problem that we have is that we would like to somehow split
>> Vv> this exe file into 10+ smaller dll files and update them if
>> needed
>> Vv> instead of expecting users to download 20mb file when they only
>> need
>> Vv> update that's 100kb.
>> Vv> Vv> Any links, suggestions would help.
>> Vv> Vv> Thanks,
>> Vv> Vv> Vlado
>> Vv>