2015 DontnetConf just passed, .NET developers got many existing news from .NET team and community. WPF is the one.
In last year, Nov 12, WPF team announced a new Roadmap for WPF. but there were not enough and details information.
But on the 2015 dontnetConf, we got more information, Microsoft will definitely continue to support WPF, and, they announce they will have the following areas of investment.
My testing Ubuntu is Ubuntu 14.04 LTS edition.
1: Add the Mono Project GPG signing key and package repository Ubuntu system:
sudo apt-key adv –keyserver keyserver.ubuntu.com –recv-keys 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF
echo “deb http://download.mono-project.com/repo/debian wheezy main” | sudo tee /etc/apt/sources.list.d/mono-xamarin.list
sudo apt-get update
When people said .NET on Linux, we know it was about Mono.
At the beginning Mono was just a small open source project which tried to help .NET application to run on Linux, Now Mono becomes to a platform, it supports multiple language such as C#, VB, Java, Python etc.
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.