How to install the original sample correctly, with reference assemblies?
I am developing a .NET class library along with some sample sources. So my solutions consist of a library, a VB sample to illustrate the library, and a setup project to deploy everything.
The sample has a project dependency on the class library, and the customization project is configured to deploy the class library (i.e. exit the .NET class library project) and VB application sources.
The problem is that the vbproj file for the VB application contains the project dependency (i.e. refers to the .csproj of the class library).
I am trying to achieve that when the sources are deployed to the client machine it is a standalone project and it relies on the (just installed) class library DLL.
I suspect I need to do some manipulation of the post vbproj installation, but since I'm new to this, I wonder if this could (I would have thought) propagate a problem that I can deal with easily?
TIA
source to share
My suggestion was to split your two projects into two solutions, one for the library and one for the VB example project.
Your VB sample project can immediately link to the library DLL directly, rather than linking to the project. This is closer to how you plan to "unwrap" this sample, so you don't need to do any post-fact manipulation.
While you are writing your library it can be trickier since you will be maintaining two projects, but if your library is mature it will clear this path.
source to share