uk_codemonkey
Jan 9th, 2006, 10:10 AM
Hi folks
Until now, any solutions that I have created using VS2002 Visual Basic have been deployed to the user's local PC using a deployment project, which has worked a treat. However, we are about to radically overhaul our network, and are looking at changing our VS applications so that they are accessed from a central location on our network (which is Windows 2000/2003).
Normally, any solutions that I create contain three or four separate project. Some of these projects are interlinked, some are self-contained. Ultimately, there is a main project which will always reference any other projects in that solution.
With all of this in mind, I have a few questions:
1. I know how to grant full-trust access to my centralised location, using CasPol. However, is it possible to automate that process, rather than having to configure each workstation individually;
2. Once I've built my application in release configuration, what do I need to copy to the central location in order for the application to work properly?
With regards to Point 2, I thought it would just be the contents of the obj\Release folder within the solution's main project. However, the only file in there is the executable for the main project, not the additional DLLs that are output by the other projects within the solution.
Hope someone can help.
TIA
Until now, any solutions that I have created using VS2002 Visual Basic have been deployed to the user's local PC using a deployment project, which has worked a treat. However, we are about to radically overhaul our network, and are looking at changing our VS applications so that they are accessed from a central location on our network (which is Windows 2000/2003).
Normally, any solutions that I create contain three or four separate project. Some of these projects are interlinked, some are self-contained. Ultimately, there is a main project which will always reference any other projects in that solution.
With all of this in mind, I have a few questions:
1. I know how to grant full-trust access to my centralised location, using CasPol. However, is it possible to automate that process, rather than having to configure each workstation individually;
2. Once I've built my application in release configuration, what do I need to copy to the central location in order for the application to work properly?
With regards to Point 2, I thought it would just be the contents of the obj\Release folder within the solution's main project. However, the only file in there is the executable for the main project, not the additional DLLs that are output by the other projects within the solution.
Hope someone can help.
TIA