V
Vagif Abilov
Hello,
We are setting up an envirnoment for daily builds, and there are a few
things in VS.NET behaviour that makes it a bit complicated. One of them is
post-build events. If you have a .NET component that should be registered
with COM+ catalog, then Visual Studio includes a post-build event with a
call to REGSVCS.EXE. The problem is that the command generated by VS.NET is
quite ugly: it includes hard-coded path of .NET Framework where REGSVCS.EXE
resides. So if some developers install Windows in C:\WINDOWS, and others -
in C:\WINXP, it will not work.
There is a macro $(FrameworkDir) supported by Visual Studio, but it looks
like it's recognized only for C++ projects - C# projects don't reconize it.
So our choice now is to copy REGSVCS.EXE (or any other tool from .NET
Framework) to a directory that VS.NET can find. This does not look elegant,
but are there any better alternatives?
Best regards
Vagif Abilov
Oslo, Norway
We are setting up an envirnoment for daily builds, and there are a few
things in VS.NET behaviour that makes it a bit complicated. One of them is
post-build events. If you have a .NET component that should be registered
with COM+ catalog, then Visual Studio includes a post-build event with a
call to REGSVCS.EXE. The problem is that the command generated by VS.NET is
quite ugly: it includes hard-coded path of .NET Framework where REGSVCS.EXE
resides. So if some developers install Windows in C:\WINDOWS, and others -
in C:\WINXP, it will not work.
There is a macro $(FrameworkDir) supported by Visual Studio, but it looks
like it's recognized only for C++ projects - C# projects don't reconize it.
So our choice now is to copy REGSVCS.EXE (or any other tool from .NET
Framework) to a directory that VS.NET can find. This does not look elegant,
but are there any better alternatives?
Best regards
Vagif Abilov
Oslo, Norway