I’m developing a .NET class library, along with some sample sources.
So, My solutions consists of the library, the sample VB to illustrate the library, and a setup project to deploy it all.
The sample has a project dependency on the class library, and the setup project is configured to deploy the Class library (i.e. the output from the .NET class library project) and the sources of the VB app.
The problem is the vbproj file for the VB app contains the project dependency (i.e. it refers to the .csproj of the class library).
What I am trying to achieve is that when the sources are deployed on the client machine, it is a self-contained project, and it relies on the (just installed) class library DLL.
I suspect that I need to do some post install manipulation of the vbproj file, but as I’m new to this, am wondering if this (i would have thought) common issue is something I can handle easily?
TIA
You could remove the “project dependency” and instead add an “assembly reference” to your VB project.