I just installed VS2015 and I'm wondering if I should use the Asp.Net 5 preview template (this is the only option I currently have in VS2015) for my new website. Does anyone know if this preview is some sort of a beta version which might be unstable? If not, why is this version called a preview version?
I didn't find much information about this preview thing in Google so I'll be happy to get some relevant information or links to explanations about this preview version.
Thanks.
ASP.NET 5 is still in beta, and is not yet released as a finished product nor recommended for production applications. It's marked as preview because of this, as it may (and will) continue to change how it does things until it reaches the RTM version.
If you are happy with the above, and want to tinker around, while understanding that updates in the coming months may break your code, then go for it! If you'd rather only write your code once and not have it break with updates, then stick with the previous ASP.NET project types like MVC 5.
Here's the roadmap/schedule for ASP.NET 5 which notes that RTM is expected to be available in Q1 2016.
Related
I am dusting off a number of old projects that we have in production and would like to upgrade the vbproj files to the latest version. Currently, ToolsVersion="12.0". New projects created in VS 2019 are using 15.0. My current projects have been repeatedly updated since something like VS 2003. However VS 2019 is not offering to upgrade them further. Although maybe I am missing something.
I plan to set up a side-by-side environment so I can use the designer content. I would really like to begin with project versions that are up-to-date. These current projects have been repeatedly updated since something like VS 2003.
A cursory review shows that the vbproj content is quite different. Is there a recommended way to upgrade? One alternative would be to create new projects using current templates and copy the source over. But there are about 32 projects that include WinForms, Web and class library projects and that's a big task. Another approach would be for me to manually merge the old and new vbproj files, something I am not sure I can safely do.
Any ideas?
VS 2019 - how to upgrade Visual Basic .NET projects
In fact, you have missed too many versions of VS and this document shows that VS2019 will not allow to upgrade VS2003 project directly.
Because there are too many different versions, there have been great changes from the project structure to the construction mechanism to various details, and some have even been removed from the new version VS.
The safest way is to upgrade the project step by step(a version by a version), but it is not unreality since VS2005, VS2008 are no longer maintained by Microsoft.
Or you can try upgrading your project step by step with VS2010 directly as an intermediate, but due to the large gap between the two, there will be various upgrade errors. And there is no such tool or easy approach to upgrade directly.
Actually, the best way is just creating new projects in VS2019 and then migrate your old project content into your new projects.
This is certainly much clearer and easier than if you were to correct errors in more than 30 projects later. And old projects with a gap of 16 years are worth the time it takes to re-create and migrate them in vs2019, which will take a long time but save you unnecessary and tedious errors.
In addition, do not forget to make a backup just in case.
Hope it could help you.
I am looking for a javascript solution which can unordered list to a treeview with checkboxes.
So far the best one I have seen is Dynatree. However, looking at the page and the fiddle , I learned that there is a designated successor named Fancytree.
I am planning to implement the solution in a production environment.
Which is the best library to use?
As of today (nov. 2013) Dynatree is the stable version.
While the core functionality in Fancytree is already pretty stable too, there still may be some changes to the API and markup. I am planning to release Fancytree early next year.
So if you want to be on the save side, use Dynatree.
If you are fine with core functionality, want to help to test and improve this open source project and are ready to modify your code every now and then: use Fancytree.
(Disclaimer: I am the author of both.)
Update 2014-05-01
Today I released v2.0.0
Dynatree is EOL. Last commit was on 19 Aug 2016.
I will support Dynatree for a while, but no new features will be added.
It is recommended to migrate to Fancytree. It's easy: see also the migration hints.
Src
I really enjoy Xamarin Studio and I'm looking for a template solution to start developing a cross devices application with MvvmCross.
But I can't find how to set a project to work with PCL and MvvmCross with Xamarin Studio.
If anyone can give me a link where I can find a tutorial to make it, it would be awesome.
I would be very pleased to contribute to this community by giving my feedback and providing some tutorial about how to start using Xamarin Studio, PCL MvvmCross and get rid of Visual Studio :D
As #duDE's answer pointed out, for working in Visual Studio on the PC in the pre-Xamarin2.0 world, there were quite detailed instructions available on http://slodge.blogspot.de/2012/12/cross-platform-winrt-monodroid.html
As various releases of Xamarin 2.0 have been released over the last month, these type of instructions have become more and more difficult to keep up to date... and this situation is likely to continue for a little while yet as Xamarin are currently adding:
.Net 4.5 (Mono 3) support
async/await support
PCL support
This work is being done with some urgency, but without any official target date - so I'm afraid there isn't any easy way to predict dates for Alpha, Beta or final availability.
For the current OSX setup, I think you can use:
the current XamarinStudio/MonoDevelop - 4.0.2
the current stable Xamarin.iOS/MonoTouch and Xamarin.Android/MonoDroid - do not use the Aplha channel
For the current PC setup, I think you can cannot use Xamarin.iOS, but you can use:
VS2010 or VS2012
the current stable Xamarin.Android/MonoDroid - do not use the Aplha channel
with just a couple of changes:
you need to add two supported framework xml files - one for Android and one for MonoTouch - you can find these on http://slodge.blogspot.co.uk/2013/03/xamarinios-with-mvvmcross-in-vs2012.html
For discussions on getting things building and running, don't use StackOverflow - instead use one of:
http://forums.xamarin.com/discussion/1549/pcls-and-mvvmcross-in-the-new-tools#latest
as a backup you can also try https://jabbr.net/#/rooms/mvvmcross
Don't even think about trying to get an MvvmCross app built - on the free version of Xamarin - it's limits are way too low for any app I've tried to build.
If you are looking for some starting app templates, use: https://github.com/slodge/MvvmCross-Templates
If you are looking for some pre-built binaries, use one one of the folders on: https://github.com/slodge/MvvmCross-Binaries - please note that portable libraries built on the Mac are not portable across to the PC (or vice versa) - they will be 'soon' but not yet.
Sorry for the fact that we don't have a neater, finished solution... we've now been fighting to hack PCLs into Xamarin for a year. However, the good news is that really soon that battle will be over and we can all get on with the apps :)
I guarantee this answer is out of date inside a week...
Xamarin.Studio 4.2 allows you to create PCL projects.
Take a look at this article: http://slodge.blogspot.de/2012/12/cross-platform-winrt-monodroid.html
Many information about using PCLs as well as some special infos about MVVMCross
I'm writing a small free tool. It's currently in Beta testing using .NET 3.5 but there's at least one aspect from .NET 4 I'd like to incorporate.
So, is it jumping the gun a bit to release .NET 4 based software?
Thx!
Wait till atleast the public release of .NET 4.0 before releasing anything other than early beta software with it.
I'm excited about alot of the new stuff too, but beta software built on a framework that is itself in beta is a recipe for disaster if you ask me.
Writing code for 4.0 might make sense. Releasing for general consumption prior to its official release seems foolish to me. Minor changes in 4.0 between now and the official release could cause your code to break. It would likely be easy to fix, but until you do your users are mad at you for putting out (what appears to them to be) a buggy program.
I read somewhere that VS2010 comes with a go-live license, meaning you can. Not sure I would, though. (See other answers...)
Well, you'd be forcing people to download and install Beta software. People may be reluctant or even unable to do this so, if nothing else, you're limiting your audience.
Also anything built with the Beta software isn't guaranteed to be compatible with the final released version.
I wouldn't go for the full framework, but including libraries like the CTP for the Task Parallel Library if your application is heavily multithreaded would be OK since you can just ship the .dll with you application and your users won't have to download anything. However, even with the TPL I would watch out, it's quirky and can slow your algorithms by an order of magnitude on things that should seemingly run just fine. The CTP is already over a year old though.
I heard from a friend that Microsoft rewrote all the Windows Workflow Foundation (WF) again and changed everything was in .Net 3.5.
Is that true?
And what about what we learned about WF in 3.0 and 3.5?
According to this article:
http://visualstudiomagazine.com/articles/2009/01/01/windows-workflow-changes-direction.aspx
Windows Workflow Foundation 4.0 is a "bottom-up rewrite with entirely new thinking...WF 3.0/3.5 will remain part of the framework and will run side by side with WF 4.0. This lets you manage the transition at a time that fits your organization's broader goals."
...which is code for, "We know we just screwed up your programming model, but we have a long term strategy, so we hope you will forgive us."
The article goes on to say that
The gains are enormous: custom
activities take center stage, and
authoring them is much simpler;
workflows are entirely declarative;
and there are three workflow flow
styles that you can combine
seamlessly. It's possible that you
could see a 10-fold improvement in the
time required to create and debug
workflows, in addition to 10- to
100-fold runtime performance
improvements.
The change is not without its detractors. In this article at DotNetKicks, the author states that "Microsoft is seriously damaging the Dot Net developer community and adoption in the industry with these half baked product releases and abrupt about-faces after shipping."
Which is why I generally wait for the 2.0 or 3.0 version of Microsoft technologies, although I made an exception for ASP.NET MVC.
We found the workflow product to be difficult to wrap your head around when it came time to pass data in and out. Scott Allen had a series of articles that did a good job describing the process, but still this was not at an easy task.
That's what the word on the street is. And on the internet. 3.0 and 3.5 will be deprecated, but still available.
Is this change not in Visual Studio 2010 beta 1? Download it, find out, and tell Microsoft what you think of it.