profile
viewpoint
Barry Nolte BarryNolte Nolte Enterprises, LLC Redmond, WA http://www.barrynolte.com

BarryNolte/condo 0

Windows WPF console application and vt100 parser.

BarryNolte/gui.cs 0

Console-based user interface toolkit for .NET applications.

BarryNolte/highlight 0

A relatively simple and extensible syntax highlighter written in C#.

BarryNolte/PyBld 0

Python based make tool

BarryNolte/VerilogLanguageExtension 0

Verilog Language Extension for Visual Studio

BarryNolte/vscode-arduino 0

Visual Studio Code extension for Arduino

BarryNolte/vscode-python 0

Python extension for Visual Studio Code

BarryNolte/Xamarin.Forms 0

Xamarin.Forms Official Home

starteddotnet-architecture/eBooks

started time in 9 days

fork BarryNolte/highlight

A relatively simple and extensible syntax highlighter written in C#.

fork in a month

startedXinyuan-LilyGO/TTGO_TWatch_Library

started time in 2 months

pull request commentgojimmypi/VerilogLanguageExtension

Added Project Template for Verilog

I'd ask why, but I stopped doing that a long time ago... :) Someday, when I'm really bored, I'll maybe, try to figure out why. Since it works with MSBuild on it's own, that must put VS in some other mode when it executes msbuild.

BarryNolte

comment created time in 3 months

pull request commentgojimmypi/VerilogLanguageExtension

Added Project Template for Verilog

Sorry for the delay, I mailed back my response 3 days ago and it didn't net posted here, checked back in today and it didn't see it.

OK, if I read the docs right, the SynchronizingObject if set to a UI control, will force the exit event to run on the UI thread instead of a random thread out of the thread pool. As long as you don’t touch the UI on the exit event, then it doesn’t matter.

Now, for not getting any output. Well, I’m not sure why, but here’s a catch… this code (Command1:Execute) will suffer the same problem as before, sort of… It’s all running on the UI thread, blocking, while the compiler is running. You’ll have to run this in a separate thread or task. VS is very good at two things, silently eating your mistakes, or failing spectacularly at your mistakes, I think you’ve hit the former.

Aha…

// this next line will freeze the IDE until process compiler completes // compiler.WaitForExit();

This is the clue, I think everything is getting eaten by VS up until this point, since the UI can’t run, then when it can, there’s nothing left to do, thus, not output. Time for some fancy asynchronous programming 😊.

BarryNolte

comment created time in 3 months

more