April 7, 2008
Hi all
I am planning to develop a solution that will comprise of about 6-8
integrated modules.
Now the user would be signing on to the solution (using module 1) and then
would have the ability of moving from one module to another. I want to tie
up some parameters with the user when he signed on, like security level of
the user, company selected, financial period selected etc.
My question is what is the best way to split an application (VB Net 2008) so
that I do not have one big EXE file.
Please note here again that the user would sign on to the application
through the first module and can then only go to other modules. The first
module would be the only and primary entry point.
Thank you.
Mike TI
Hi all
I am planning to develop a solution that will comprise of about 6-8
integrated modules.
Now the user would be signing on to the solution (using module 1) and then
would have the ability of moving from one module to another. I want to tie
up some parameters with the user when he signed on, like security level of
the user, company selected, financial period selected etc.
My question is what is the best way to split an application (VB Net 2008) so
that I do not have one big EXE file.
Please note here again that the user would sign on to the application
through the first module and can then only go to other modules. The first
module would be the only and primary entry point.
Thank you.
Mike TI