 |
|
|
I have some solution those I want to aumatically rebuild but one of them contains web reference that need to update during rebuild process. Using recommendations in this article it is possible to automate rebuild of all solutions but not web references
|
| Sign In·View Thread·PermaLink | |
|
|
|
|
|
|
It always prints out the log, and it keeps a time stamp.
I tried to do a realtime log monitor but VS has a lock on the log file so it can't be read.
public int Build(string solutionFile, string solutionConfig)
{
// get temp logfile path
string logFileName = System.IO.Path.GetTempFileName();
Console.WriteLine("Building: " + solutionFile);
Console.WriteLine("Built Started At: " + DateTime.Now);
DateTime LStartTime = DateTime.Now;
// populate process environment
System.Diagnostics.ProcessStartInfo psi = new System.Diagnostics.ProcessStartInfo();
psi.FileName =@"devenv.exe";
psi.ErrorDialog = true;
psi.Arguments = "\"" +solutionFile +"\"" + @" /rebuild "+ solutionConfig + " /out " + logFileName;
// start process
System.Diagnostics.Process p = System.Diagnostics.Process.Start(psi);
// instruct process to wait for exit
p.WaitForExit();
// get return code
int exitCode = p.ExitCode;
// free process resources
p.Close();
// if there was a build error, display build log to console
System.IO.TextReader reader = System.IO.File.OpenText(logFileName);
errorLog = reader.ReadToEnd();
reader.Close();
System.Console.WriteLine(errorLog);
Console.WriteLine("devenv.exe returned exit code: " + exitCode);
Console.WriteLine("Build Ended At: " + DateTime.Now);
Console.WriteLine("Build Took: " + (DateTime.Now - LStartTime).ToString());
System.Console.WriteLine("Press Enter to Continue...");
System.Console.Read();
// delete temp logfile
System.IO.File.Delete(logFileName);
// return process exit code
return exitCode;
}
|
| Sign In·View Thread·PermaLink | |
|
|
|
|
|
|
As the title says... Does anyone know how to display the build log whilst command line builds are in progress?
I find it very annoying to just have a cursor blinking at me (I can see it now) when I really want to know how far along the build is.
I have tried a tail util on the build log, but that does not work.
Anyone any ideas?
DAve
|
| Sign In·View Thread·PermaLink | |
|
|
|
|
|
|
Basically you have to set the RedirectStandardOutput and RedirectStandardError values of the ProcessStartInfo object to true and then read the StandardOutput and StandardError streams. Make sure this all gets done in a seperate thred otherwise you'll end up locking up the application until devenv finishes.
check out the Launching a process and displaying its standard output article for sample code, et. al.
|
| Sign In·View Thread·PermaLink | |
|
|
|
|
|
|
Woh!
That was a reply from the past... I barely remember asking the question 
The problem has now vanished since recent versions of .NET output to the console that the command line was run from.
Thanks for your help though that link was very usefull for another thing I'm looking at.
Cheers
DAve
|
| Sign In·View Thread·PermaLink | |
|
|
|
|
|
|
I redirected the StandardOutput and StandarError, I have done this with other processes but with devenv I just get "" "" for both objects. If I dont redirect the output I can see the message in the console windows, but cant get it from there.
Here's my code:
//Somewhere else I call it like:
//return base.Compilar("\""+ pathSolutionFile+"\" /build Debug");
protected string Compilar(string arguments)
{
System.Diagnostics.Process process = new Process();
if(pathCompiladorDirectory != null)
{
process.StartInfo.WorkingDirectory = pathCompiladorDirectory;
process.StartInfo.FileName = pathCompiladorDirectory + ejecutable;
}
else
process.StartInfo.FileName = ejecutable;
process.StartInfo.Arguments = arguments;
process.StartInfo.UseShellExecute = false;
process.StartInfo.RedirectStandardOutput = true;
process.StartInfo.RedirectStandardError = true;
process.Start();
Teller outputTeller = new Teller(process.StandardOutput);
outputTeller.LeerEvent += new Teller.Leer(outputTeller_LeerEvent);
Thread outputThread = new Thread(new ThreadStart(outputTeller.Lee));
outputThread.Start();
Teller errorTeller = new Teller(process.StandardError);
errorTeller.LeerEvent += new Teller.Leer(errorTeller_LeerEvent);
Thread errorThread = new Thread(new ThreadStart(errorTeller.Lee));
errorThread.Start();
process.WaitForExit();
process.Close();
while(errorThread.IsAlive || outputThread.IsAlive);
return output + System.Environment.NewLine + error;
}
protected void errorTeller_LeerEvent(StreamReader reader)
{
error = reader.ReadToEnd();
}
protected void outputTeller_LeerEvent(StreamReader reader)
{
output = reader.ReadToEnd();
}
protected class Teller
{
public delegate void Leer(StreamReader reader);
public event Leer LeerEvent;
StreamReader reader;
public Teller(StreamReader reader)
{
this.reader = reader;
}
public void Lee()
{
if(LeerEvent!=null)
LeerEvent(reader);
}
}
The weird thing is that this code is working for other compilers, but not with devenv
|
| Sign In·View Thread·PermaLink | 5.00/5 |
|
|
|
|
|
|
hi guys!
i got a problem. vs.net doesnt start.
instead i get an error message.
the pop-up window says: "ms development environment has determined a problem und got to be shut down" (sorry, translation from german version)
"an unhandled exception has been caught by the vsw exception filter."
appname:devenv.exe appver:7.0.9466.0 modname: hxds.dll
modver: 2.1.9466.0 offset: 0001e84f
im anything but skilled with this stuff, maybe one of you guys can help me out.
thank you!
|
| Sign In·View Thread·PermaLink | |
|
|
|
|
|
|
Hi,
hätte die deutsche Meldung auch verstanden ,)
could you please give me more detailed information about what you did, i guess you launched the console application via context menu item to build a solution. If you start devenv.exe from command line, everything works as expecteded ? Only if you use the console application it crash ?
.:Greets from Jerry Maguire:.
|
| Sign In·View Thread·PermaLink | 1.00/5 |
|
|
|
|
|
|
|
|
|
I have a problem trying to run it from the web server. It's weird - if someone is logged on to the console or using terminal client - it works. When noone is logged on - it doesn't.
I set all the neccessary permissions etc, but unless I log on to the server "devenv.exe" is freezing - not consuming the CPU, but doesn't do anything and the buildlog.txt file is locked until I kill the process.
Do you have any ideas why it happens like that and how can I fix it?
|
| Sign In·View Thread·PermaLink | |
|
|
|
|
|
|
Hi Nikolay,
hmmm, now for every user ( calling ) the buildlog.txt is created in his user profile directory where his permissions are granted.
Did you try to start devenv.exe with a batch call ? If devenv.exe then also freeze, it should not be a problem of the console application. No good solution for you, i know. If you find the error please drop me note, thanks.
I never try run this little thing on a server, just test it on my client.
.:Greets from Jerry Maguire:.
|
| Sign In·View Thread·PermaLink | |
|
|
|
|
|
|
The idea is to minimize the uploads neccessary and ease the development over the internet. And I don't want to upload the binaries all the time...
It works perfectly as a batch file.
It works perfectly when I call it from the console application.
It works perfectly when I start the console application from IIS on my machine.
It works perfectly when I start the console application on the server from my machine only while I'm logged on to it. Once I log off and the program stops working... isn't that weird ?
If you or someone knows why it's freezing I'll be very thankful to learn 'why'.
(Eventually if I find a way around or figure out why it happend like that I will let you know)
Once again thanks for the article - helped me a lot ( yes, I keep the connection open all the time now )
|
| Sign In·View Thread·PermaLink | |
|
|
|
|
|
|
|
|
|
Hi,
i experience problems with the tool if a project path that contains spaces. After changing on line in the code the tools works for me on those project paths.
Orig:
psi.Arguments = solutionFile + @" /rebuild "+ solutionConfig + " /out " + logFileName;
Modified:
psi.Arguments = "\"" +solutionFile +"\"" + @" /rebuild "+ solutionConfig + " /out " + logFileName;
Nice tool, thanks and regards, Christian
|
| Sign In·View Thread·PermaLink | |
|
|
|
|
|
|
|
|
|
You could create a REG file to add this to the registry automatically. I've done this so anytime I install VS, I can just execute the REG file to create the context menu items.
Create a text file and add the following text. Then rename the text file to "something.reg". Then to add it to the registry just execute the reg file. This text adds both 'Build Debug' and 'Build Release' to the context menu (using XP reg version 5.00).
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\VisualStudio.Solution\Shell\Build_Debug]
@="Build Debug"
[HKEY_CLASSES_ROOT\VisualStudio.Solution\Shell\Build_Debug\command]
@="\"C:\\Program Files\\Microsoft Visual Studio .NET\\Common7\\IDE\\devenv.exe\" \"%1\" /rebuild Debug"
[HKEY_CLASSES_ROOT\VisualStudio.Solution\Shell\Build_Debug\ddeexec]
[HKEY_CLASSES_ROOT\VisualStudio.Solution\Shell\Build_Debug\ddeexec\Application]
@="devenv"
[HKEY_CLASSES_ROOT\VisualStudio.Solution\Shell\Build_Debug\ddeexec\Topic]
@="System"
[HKEY_CLASSES_ROOT\VisualStudio.Solution\Shell\Build_Release]
@="Build Release"
[HKEY_CLASSES_ROOT\VisualStudio.Solution\Shell\Build_Release\command]
@="\"C:\\Program Files\\Microsoft Visual Studio .NET\\Common7\\IDE\\devenv.exe\" \"%1\" /rebuild Release"
[HKEY_CLASSES_ROOT\VisualStudio.Solution\Shell\Build_Release\ddeexec]
[HKEY_CLASSES_ROOT\VisualStudio.Solution\Shell\Build_Release\ddeexec\Application]
@="devenv"
[HKEY_CLASSES_ROOT\VisualStudio.Solution\Shell\Build_Release\ddeexec\Topic]
@="System"
Anyway, thanks for the article. It is a good idea.
-Ryan
|
| Sign In·View Thread·PermaLink | |
|
|
|
|
|
|
Hi Ryan,
you're right, this is a good reusable solution, like you can see i add a example bat and reg file.
At the time i wrote this article, i got the feeling that most people don't like to "work" on the registry just to extend a context menu item. But it's shure a fast and reusable way to do that.
thanks
.:Greets from Jerry Maguire:.
|
| Sign In·View Thread·PermaLink | |
|
|
|
|
|
|
Sorry for my bad english and the german screenshots, but i had no english XP/VS.NET by the hand.
.:Greets from Jerry Maguire:.
|
| Sign In·View Thread·PermaLink | 2.00/5 |
|
|
|
|
|
|
Oh, and your keyboard was not working all right, so you needed to change some 'S' for '$', right? 
I see dumb people
|
| Sign In·View Thread·PermaLink | 3.00/5 |
|
|
|
|
|
|
I agree totally with your point. Microsoft developers shouldn't complain AND develop with Microsoft technologies. It's like having your cake and squashing it too. This is a really tacky approach and someone might mistake you for a linux junkie...or worse yet, a Mac luser!
"Well, I wouldn't say I've been missing it, Bob." - Peter Gibbons
|
| Sign In·View Thread·PermaLink | |
|
|
|
|
|
|
Hi,
hmmm.. what should i say, i really like microsoft, and my daily business is C# with Visual Studio. I think your feedback isn't really fair.
.:Greets from Jerry Maguire:.
|
| Sign In·View Thread·PermaLink | |
|
|
|
|
|
|
I wouldn't worry about it ... too much political correctness has blinded people. And besides, with $36 billion in cash assets I'd say Microsoft was the very definition of ca$h money!!!
|
| Sign In·View Thread·PermaLink | |
|
|
|
|
|
|
|
|
|
Oh lighten up Francis. The guy can say whatever he wants. Not everyone tows the line in the same way. You could easily argue that Microsoft's licensing policies are ALL about the $$$. Blah Blah Blah.
|
| Sign In·View Thread·PermaLink | |
|
|
|
|
|
|
|
