Microsoft announced new update for ASP.NET 5 and released Visual Studio 2015 CTP 6 on Monday. So I think I should try the new features earlier since I get spare time today.
Let me start from Visual Studio 2015 CTP version. I have not tried it yet. Because it is still a preview version, so I decide to install it in Windows 10 tech preview system.
Actually I might not want to try this time if I did not read Scott Gu’s blog:
When I opened an old .NET project in Visual Studio 2013, I got the following error when I tried to rebuild the project:
Error 1 An error occurred while signing: Failed to sign bin\Release\app.publish\xxxx.exe. SignTool Error: No certificates were found that met all the given criteria. xxxx
The reason should caused by the old .NET framework platform about ClickOnce manifest certificate.
I tried to use the traditional way to get an Windows form application path:
string applicationPath = “”;
applicationPath = Application.ExecutablePath;
Visual Studio 2013 Update 4 released in Nov 12, 2014. I am going to update my local Visual Studio 2013 today.
When you have a program which needs .NET Framework 2.0, but your Windows system is Windows 8; or, you are a .NET developer, you have old projects were built based on .NET Framework 2.x and you can not convert these projects to newer .NET Framework editions on Windows 8. How can you do ?
Yes, install .NET Framework 2.x.
OK, you searched internet and get .NET Framework 2.x packages, you are ready to install it on Windows 8, but wait, you find nothing happened when you try to install !
We had a post about “Silverlight application compile failed in Visual Studio 2013”, but this time after we did the steps which was introduced, we still got compile failed.
We tried to moved current Silverlight application to another pc which was installed visual studio 2013, we found there were some references gone.
We tried to use NuGet manager and installed some packages but still not work. so what we did was just add those missed reference (dll files) manually in Visual Studio 2013.
Today we did Visual Studio 2013 Update 3 since Update 4 RTM is coming, so we think it is the time to update to 3, should be maturity after real users used.
Compared with MODBUS protocol, if your device will be on Web, you might better consider use WSD protocol: Web Services on Devices.
Here is Microsoft WSD development information.
When you use Windows Form Listview control, you will see a strange problem: you added columns, but the columns can not showing up in the designer panel in Visual Studio.
This is from Microsoft design: they set default Listview control view property to LargeIcon, maybe they think ListView control is not like regular DataGridView control, the view should be use Icon showing style?
Here is the Dev Center site of Microsoft. You can find dev information about Desktop, Hardware, Web etc.
This is about desktop dev. You can see an info about how to choose your tech, We can see for example the different between WPF and Windows Form:
.NET Windows Presentation Foundation (WPF): This is the preferred technology for Windows-based desktop applications that require UI complexity, styles customization, and graphics-intensive scenarios for the desktop. WPF also takes advantage of XAML views. You can leverage the new simplified asynchronous capabilities (async/await) in .NET 4.5. WPF development skills are similar to Windows Store development skills, so migration from WPF to Windows Store apps is easier than migration from Windows Forms.
.NET Windows Forms: .This was the first UI technology in the .NET Framework for building desktop applications. It is still a good fit for many business desktop applications. Windows Forms is easier to use and lighter weight than WPF for simple scenarios. Windows Forms does not use XAML, so deciding later to extend your application to Windows Phone or Windows Store entails a complete re-write of your UI.
For business application technology guide, you can download from here.