Build problem with C++/CLI dll.

[Kei]

I'm working on a VS 2005 solution which includes a project with WPF/
C# for UI work, and several projects with C++/CLI for business
logic.

I often ran into a problem where C++/CLI dlls cannot be built because
IDE has these dlls loaded.

I believe IDE has to access to these dlls while I'm working on WPF/C#
because it has to know the types defined in the dlls.

Well, I work on WPF/C# and C++/CLI projects on paralell, and being
unable to built C++/CLI dlls after I work on WPF/C# code is getting
really troublesome.

I wonder if anyone can suggest any solution.

Anyway to tell the IDE to unload the assembly dlls?
Thanks in advance,

Kei

[Carl Daniel [VC++ MVP]]

Kei wrote:

I'm working on a VS 2005 solution which includes a project with WPF/
C# for UI work, and several projects with C++/CLI for business
logic.

I often ran into a problem where C++/CLI dlls cannot be built because
IDE has these dlls loaded.

I believe IDE has to access to these dlls while I'm working on WPF/C#
because it has to know the types defined in the dlls.

Well, I work on WPF/C# and C++/CLI projects on paralell, and being
unable to built C++/CLI dlls after I work on WPF/C# code is getting
really troublesome.

I wonder if anyone can suggest any solution.

Anyway to tell the IDE to unload the assembly dlls?

Sadly, no. Usually even closing the solution is not sufficient - you have
to completely recycle the devenv.exe process.

If you have a reproducible scenario, please open a bug report against VS2005
on Connect - http://connect.microsoft.com/VisualStudio/feedback.

VS2002/3 were riddled with "file locked by another process" bugs, many of
which were fixed in 2005, but it sounds like not quite all of them yet!

-cd