I code for micro controllers and also create GUI in UWP. With each passing year I feel coding for PC is taking more effort while coding for the embedded systems is becoming more easy.

PSoC IDE from Cypress Semiconductor is a revolutionary idea for coding micro controllers. But the irony is a Text based IDE like Arduino is more popular than the PSoC idea. The Arduino IDE hides under the hood all aspects of the microcontroller, while the PSoC IDE exposes every single aspect of the micro controller with graphics to make life easy for the embedded developer.

I see neither of these strategies happening in the windows world and hence the frustration coding for the PC.

Liscence PSoC IDE to delve into the details of customization of UWP GUI controls. Adopt Arduino like approach for text based entry greatly hiding the details under the hood and let the text based entry also be with strict VB6 syntax.

I got to say, Microsoft has everybody confused as heck... they kill off windows Mobile... but the Windows 10 programming books on the market still push UWP... so you download the code examples off of docs.microsoft.com and they want you to install a Windows Phone emulator just to run the sample code... WTF Microsoft? you people are confusing the **** out of the public... I look and I see that Microsoft's team is converting Control people into a UWP application, yet the outward signs from their document website is that UWP is shutdown because it based on windows mobile emulator in the samples zip file for UWP applications.... I don't mind using UWP XAML over WPF XAML... its just different controls... I just can't figure out why we still need to download the windows phone emulator just to see the sample code in the giant zip bundle... everytime i do that it makes me think UWP is dead and i'm wasting my time... actually, the other thing that annoys me around those sampe files is the "common" directory... I don't want to look at C++, javascript, and common directories... just put it all in one directory...please... people get annoyed when files get split up like that... duplication is ok... just use a script to keep them the same....for each bucket c++, c#, javascript,et c...

I am reposting a idea proposed in 2013 which did not get a second vote:

If Bill Gates was watching he would have voted a million times for this idea.
If this was done in 2013 when Original Poster (OP) disclosed, Lumia would not have died and M$ would not have incurred the millions of dollar loss.
OP is a visionary and I am opening it again.

--- original post ----
MS Small Basic is an excellent language
inspired by our old Basic
I trained with him young people from 16/17 years in the secondary
It allows to understand the basics of programming, certanly
In addition with a simple function
is migrated (graduate) to VB.NET ( why not to C# or another?)
It allows the student concentrate on the problem to solve
without complicated with motley syntax
and greatly improves reasoning ability of a young people
which may be, after school, a public accountant or an engineer, who know?
Not necessarily they will be professional programmers
And finally S.B. is being compiled C # and ends as MSIL virtual machine of .NET
I think the basic philosophy of .NET
is that should be indistinct what language you are using
instead, the power of the algorithm thought
Please visit http://smallbasic.com
Regards

The design view in Visual Studio has become so slow as to be almost obsolete.
Originally I was bewildered by the inevitable 'Not Responding' message, as I'm working on a top range Surface Pro 3.

Killing every other process not required has made no difference.

I even briefly installed Visual Studio on a research PC for high performance computing, with 920 I7 processors, and even it hangs!

I've now spent days researching how to resolve this, and have made one very interesting discovery: I am one of the very few people who still use Design Mode in Visual Studio, as everyone else has already abandoned it due to the appalling responsiveness! Instead they use a browser to view the design.

So I am, with much regret, going to probably become one of those developers who pretends that the designer doesn't exist. I just can't stand wasting hours each week looking at the 'Not Responding' message at the top of the screen.

Please improve the Design View so that we can use it again!

In Visual Studio 2017, all editions, when, in the WPF XAML, an object property is bound to a UI XAML control, the reference link on the class source code should reflect this 1 reference in the reference count above the property and the link to that reference could point to the XAML element/control.

Typically, each binding has these four components: a binding target object, a target property, a binding source, and a path to the value in the binding source to use.
For example, if you want to bind the content of a TextBox to the Name property of an Employee object, your target object is the TextBox, the target property is the Text property, the value to use is Name, and the source object is the Employee object.

At present the Visual Studio 2017 IDE does not show the 1 reference count on the Name property in the Employee class, even though it is used as the property of a source object and used in a binding.

Could this be changed in a later Visual Studio IDE release?

This is an extremely easy and non-breaking way to solve the long-running problem of undesired spaced between <Run> elements in a <Run> collection. Not having inner text between the <Run> elements in the XAML source doesn't really work because generally we want the XAML editor to support reformatting by nicely breaking <Run> elements onto separate lines. Extending xml:space to support "remove" means existing code will not be broken, but developers can add the tag to instruct the parser to discard the entire inner text if it is all whitespace. If MS is worried about a conflict with possible future XML spec changes, then introduce an MS-specific tag that performs the same function.