Bruce,
In addition to the other comments.
It is hard to believe that VB does not have a way to build using
different parameters from one project. But I guess it is so?
VB *does* have a way to build using different parameters!
However by default it is turned off. Use "Tools - Options - Projects
and Solutions - General - Show Advanced Build Configurations" to enable
or disable the feature. Once you enable this option you will have both
Release & Debug builds available.
The caveat is, there are not different References based on Release &
Debug builds per se.
What I normally do is use output folders to hold my Release & Debug
builds of my C++, VB, or C# projects, rather then use file names. Then
I will put the C++, VB, or C# projects all in one solution. Where each
project references the other project, *by project* (not file!) This way
the Release build of the VB project will use the output of the Release
build of the C++ project, likewise the Debug build of the VB project
will use the output of the Debug build of the C++ project. Considering
that I build the entire solution...
Having said that I suspect (but have not tested) that you could change
the output name of the C++ assembly within the respective Debug or
Release configuration & the respective VB build will respectively use
named C++ assembly. Again based on using Project references within a
solution & not file references. Again I have not tested this theory.
--
Hope this helps
Jay B. Harlow
..NET Application Architect, Enthusiast, & Evangelist
T.S. Bradley -
http://www.tsbradley.net
On Dec 26, 9:11 pm, Bruce <B...@nospam.comwrote:
Stephany Young wrote:
Now I can see what you are attempting.
Assuming that your 'external assembly' was also developed in VS 2005, then
simply add your 'external project' to your current solution, change the
reference to it to be 'project' rather than 'file', then, when you compile
your current project in 'debug', it will use the 'debug' version of your
'external assembly' and when you compile your current project in 'release'
it will use the 'release' version of your 'external assembly'.But the external assembly is written in C++, so there are two different
file names for the assembly MyAssemblyD.Dll for debug and MyAssembly.DLL
for release.
Plus remember that these are sample VB projects so, once if I
distribute them then they will not work because the person getting the
samples will not have my project.
I would have to change the VB project anyway so I might as well switch
between the debug and release version of the external assembly DLL.
It is hard to believe that VB does not have a way to build using
different parameters from one project. But I guess it is so?
Bruce
--
Bruce E. Stemplewski
GarXface OCX and C++ Class Library for the Garmin GPSwww.stempsoft.com