G
Guest
Forgive me if this is the inappropriate forum to post this, but I found
MSBuild.exe in the framework directory so it seems right to me
Also forgive me if this duplicates an existing post. I posted this issue the
other day, and it seems to have disappeared. (I have way too many posts not
be there when I look for them!!!)
Finally forgive me that this posting is not as complete as the original.
I've made progress so I've had to leave out the error numbers that were part
of the original.
Now on to the issue:
The MSBuild documentation implies that all you have to do is point it at the
proj files maintained by the IDE and it will run.
It appears to be even nicer than that. Start MSBuild in a folder with a
single sln file and it will find and use it. Impressive!
HOWEVER, it may or may not run without modification to the projects. I've
had to do both of the following:
1) Add references to a library that was lower in the inheritance stack than
those needed by the IDE. The projects being compiled didn't refer to this
library, but forms were derived from forms that did refer to the library.
(I've lost track of how many layers deep the inheritance of the main program
window is from Windows.forms.form. It's a bunch.)
2) I had blanks in the names of icons included in the resources and they had
to be removed. This has been documented by others elsewhere.
I finally came to a show stopper. I'm getting
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Microsoft.Common.targets(2071,9):
error MSB3188: Assembly BLAHBLAHBLAH must be strong signed in order to be
marked as a prerequisite.
No place have i marked BLAHBLAHBLAH as a prerequite. I'm not using strong
signing precisely because "the directions" which i've actually read of a
change discourage it for my target environment.
I get this error occasionally in the IDE with various of the libraries in
the project being the culprit. To solve the problem there, i just zap all the
bin and obj folders and rebuild. (I zapp directories so frequently I wrote a
program to do it. It's usually because forms get errors when I attempt to
display them.)
Zapping directories immediately before calling MSBuild makes no difference.
SUGGESTIONS please.
Regards,
Al Christoph
Senior Consultant
Three Bears Software, LLC
just right software @ just right prices @ 3bears.biz
Microsoft Certified Partner (ISV)
Coming soon: Windows Mail for Vista.
MSBuild.exe in the framework directory so it seems right to me
Also forgive me if this duplicates an existing post. I posted this issue the
other day, and it seems to have disappeared. (I have way too many posts not
be there when I look for them!!!)
Finally forgive me that this posting is not as complete as the original.
I've made progress so I've had to leave out the error numbers that were part
of the original.
Now on to the issue:
The MSBuild documentation implies that all you have to do is point it at the
proj files maintained by the IDE and it will run.
It appears to be even nicer than that. Start MSBuild in a folder with a
single sln file and it will find and use it. Impressive!
HOWEVER, it may or may not run without modification to the projects. I've
had to do both of the following:
1) Add references to a library that was lower in the inheritance stack than
those needed by the IDE. The projects being compiled didn't refer to this
library, but forms were derived from forms that did refer to the library.
(I've lost track of how many layers deep the inheritance of the main program
window is from Windows.forms.form. It's a bunch.)
2) I had blanks in the names of icons included in the resources and they had
to be removed. This has been documented by others elsewhere.
I finally came to a show stopper. I'm getting
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Microsoft.Common.targets(2071,9):
error MSB3188: Assembly BLAHBLAHBLAH must be strong signed in order to be
marked as a prerequisite.
No place have i marked BLAHBLAHBLAH as a prerequite. I'm not using strong
signing precisely because "the directions" which i've actually read of a
change discourage it for my target environment.
I get this error occasionally in the IDE with various of the libraries in
the project being the culprit. To solve the problem there, i just zap all the
bin and obj folders and rebuild. (I zapp directories so frequently I wrote a
program to do it. It's usually because forms get errors when I attempt to
display them.)
Zapping directories immediately before calling MSBuild makes no difference.
SUGGESTIONS please.
Regards,
Al Christoph
Senior Consultant
Three Bears Software, LLC
just right software @ just right prices @ 3bears.biz
Microsoft Certified Partner (ISV)
Coming soon: Windows Mail for Vista.