Good Evening,
To all who know Microsoft's upgrade policy. I own VS6 Enterprise. Is VS6 Enterprise eligible for upgrade? I also own pro vs 2005/2008 but would like the enterprise edition upgraded. I have found posts that say yes and no. What is the real policy?
Thanks again for your comments. I love stack over flow!
Brennan
The short answer: Microsoft Licensing is confusing as hell. The best way to get a good answer on this:
Go here to the Visual Studio Pricing Page
Click the Price Comparison Chart tab
Click the Request a call back link
This way you'll get someone who can give you a definite answer calling you back (same day when I had a question a few weeks back).
My guess is "no". It's like asking what's the upgrade policy from Windows 95 to Windows 7. Too many generations in the middle.
Related
What is the best process of moving a 200+ MB DotNetNuke site from Professional to Community edition? I am asking the Stackoverflow community since DotNetNuke's standard line is "there is no supported option to switch from PE to CE", or to contact their customer support. However DNN support told a fellow team member tell us that it was not possible to go from Professional to Community, so that was a waste of time.
Based on research there are a couple possibilities for doing this:
Create a new Community Install and then module by module going through and moving it piecemeal. Here - http://www.dnnsoftware.com/forums/forumid/0/threadid/427840/scope/posts
Make backups of the Professional and then install the Community Edition over it, and then go through the web.config and verify that each piece is correct. Here - http://fl2rs.com/downgrading-dotnetnuke-from-professional-to-community-edition/
Which one has the most success of converting DotNetNuke Professional Edition to Community Edition? Also, if you know of a better method please share. Thank you for your time.
Edit
Looking back at this question the only real way to convert a complicated site is to basically rebuild it which I did successfully. And if you are trying to switch from an older version of Professional to a newer version of Community even more so. I would also like to note that going to Community was the correct decision since none of the extra functionality we even used, and their support was never helpful anyway.
I don't think there's a built-in downgrade feature from Professional to Community Edition. As it was noted here in this question, DNN professional and DNN Community Edition share the same codebase. In other words, DNN Pro is DNN CE with some extra built-in extensions such as document manager, impersonate user, different caching, etc. That means 99.9% of modules and skins will run fine in either edition.
Option 1: Seems tedious but would surely work.
Option 2: I would make a backup copy of the site on a development machine and try to do it there before attempting it on the production server. Please post the results for this if you try it.
Good luck.
Option 1 would work, but I'm not sure about Option 2.
I've heard that this is not supported by DNN, but if you open a support ticket, they can walk you through the process.
This is what I found in their support forum: http://www.dnnsoftware.com/answers/cid/414288
If you have troubles with this, I've found DNN on Social Media (G+ and their forums) are more responsive. Sometimes a little prodding is needed.
Late to the party on this one - another option might be to do a portal/site export and then import it into a CE version. It has its own problems with modules that do not support this but if you are HTML content heavy then you can do it.
Does anyone have a tutorial that they could point me too. I am kinda confused about some of the steps in the wizard for install Shield 2010 limited edition.
Here's a walkthough:
http://codesmartnothard.com/InstallShieldLimitedEditionForVisualStudio2010Walkthrough.aspx
Personally though LE feels like a highly crippled adware version of InstallShield. If you don't push it very far you'll be OK but I'm betting Flexera is really counting on you needing to upgrade.
I actually used it and it works fine for me (much better than the msi).
I would like to state that this product is highly unstable and crashed VS 2010 constantly.
My solution was:
1) Unload installation project unless I am releasing a version.
2) Use it carefully and not stress this component
3) Learn to use VS 2010 in safe mode :)
I really want to upgrade to Visual Studio 2010. But since I do a lot of development for the Pocket PC version of Windows Mobile I cannot. (I develop for a Symbol device that does not support Windows Phone 7, so that is not a option.)
Does any one know any kind of time frame of when Microsoft plans to add support for Smart Device Projects into Visual Studio 2010?
Update: Since this is looking less and less likely without intervention from the users, Please go here and vote for this feature.
Microsoft's current public statement says that, apart from Windows Phone 7 development, there will not be Smart Device Application Development added to Visual Studio 2010.
This obviously raises concerns and has implications for a lot of people, and there are more than a few of us lobbying Microsoft very hard to change that plan and to get them to include some sort of support for Smart Device programming outside of Windows Phone.
I'm hopeful, maybe even optimistic, that their stance will change and that we will get something - even if it's only CF 3.5 targeting actual hardware (i.e. no emulator support) - at some point down the road. Right now they've got all hands on deck trying to get Windows Phone out the door, and until that happens, I wouldn't expect much for resource allocation toward other device features.
So what does that actually mean? In my mind I wouldn't postpone installing VS2010 until they have device support. My guess is it won't happen until early next year at the absolute earliest and realistically I would say mid to late next year if it happens at all. Again, I'm optimistic that it will, but I'm also a realist, so I'm not going to base my business decisions and future on it happening.
Add your support to the following Microsoft Connect Item, it's had quite a bit of interest being the 3rd highest voted suggestion so far.
http://connect.microsoft.com/VisualStudio/feedback/details/595712/no-support-for-windows-ce-and-compact-framework-development-in-vs2010
Through private conversations I've had with the Customer Advocacy Team at MS it would appear that they are really digging their heels in over this. MS reneged on promises to include Smart Device Framework support in VS2010 early on in the product life cycle.
It is really frustrating because at some point the development tools will fragment and you'll end up with having to maintain separate development, source control and build systems for targeting Windows CE. Who is to say that the tools will even work on future versions of Windows either or even if they will live side by side with future versions of VS. Remember this lack of support also hurts people doing unmanaged code on CE too.
MS is doing a great job of remaining silent here, the silence is already causing people to look at alternative platforms. Without a statement of intent no business is going to invest in Windows CE development without knowing the future of the OS and the tools to develop on it.
All recent Visual Studio versions can be installed side by side. You could upgrade now for desktop development, then when smart device support is rolled out, migrate your projects to VS2010.
http://social.msdn.microsoft.com/Forums/en/setupprerelease/thread/fce95ec7-728d-41d1-ab13-74a2fd3a4136
I am forced to have two VS installations side by side. However, another issue - that is causing me more pain is that TFS 2010 doesn't work with VS 2008 - there is a plugin, of course, but there are many issues with it which make it unusable.
So to have source control, I have installed SVN on my machine.
Microsoft once again, has proven that they have no concern for the devs at all. Their tools don't work together, backward compatibility is not there, all of which makes their dev tools a big load of crap.
MS replied to that connect issue:
Hi folks,
In the first quarter of 2013, we plan to provide tooling for Visual
Studio 2012 to create apps for Windows Embedded Compact v.Next. We’ll
be announcing more details in September, including the roadmap for
.NET CF. You can find more details this Fall in the Windows Embedded
Compact website at http://www.windowsembedded.com.
thanks, Doug Turnure Visual Studio PM
Is anyone out there using S#harp Architecture with VS 2010/.Net 4.0? We are looking for a good ASP.Net MVC framework, and the guys here are already familiar with NHibernate and Spring.Net, so S#harp Arch seems like a good fit. However, they are rolling out VS2010 this week, so we need to know if/how well it will work in VS2010.
Thanks in advance.
S#arp Architecture 1.5 has been released. It provides support for both VS 2008 and VS 2010. The latest version is 1.5.2. You will find the download at:
http://github.com/codai/Sharp-Architecture/downloads
I'm answering my own question. I found this post after more thorough searching of the Sharp Architecture group, which was posted on April 7th:
Eric,
I hate to be the bearer of bad news but, this version DOES NOT
support VS 2010. Once v1.5 is
released, I will concentrate on VS
2010 support as well as migrations.
Then we are off to EF 4 support. While
I realize VS 2010 is coming on the
12th (or so I've heard), Billy and I
both felt that supporting two
templates was not a good idea given
the time maintaining one takes. With
that said, v1.5 will be the last
version to support VS 2008. All
future versions will support VS 2010
until another version comes out. Now
if you want to get it working and get
a wiki page together, I for one would
be most appreciative.
Cheers,
Alec Whittington
With the upcoming release of Visual Studio 2010, and all the lovely new features in C# 4.0, I would really love to update from 2008. However, over the last few years, I've managed to get student pricing, or even free versions via the MSDN Academic Alliance.
Now I am no longer a student.
I can't seem to justify the $AU500 pricetag of even the Standard version for what is at the moment, essentially a hobby. As much as I may like for it to be, it just isn't paying the bills.
So, I've read on the Microsoft site that there's no non-commercial clause in the Express version EULA which is good because I do the occasional bit of paid work in it. How much is missing from the Express version though, compared to Professional (what I use currently, and what the 2010 beta is)? Am I likely to go through withdrawal pains as I reach for something that just isn't there?
As far as addons go, the only one I've really played with is VisualSVN, and I can live with just using TortoiseSVN manually. Anything else I should be aware of?
Version comparisons can be found here: (For 2008) (Edit: A far more in depth document can be downloaded from here)
The things that leap out to me as features I wouldn't want to be without are:
Extensibility (no plugins like VisualSVN or Resharper)
Source Code Control
Remote debugging
64-bit compiler support (x64) (from the first link, though the document implies you can make 64bit apps...)
SQL Server 2005 integration
No setup projects (for making MSI installers)
Limited refactoring
Some missing debugging tools (especially the threads window)
If you can live without those (and the other limitations that wouldn't bother me personally) then I guess that you'll get by with Express just fine.
Final thought: Express isn't your only option for free .net development, there is also SharpDevelop which has some advantages (SVN integration, compact framework support) over Express. Though I'm sure it has many limitations too.
Do you do any entrepreneurial work? If you're building the next killer app, check out BizSpark: http://www.microsoft.com/bizspark/
There is new program now available from Microsoft to allow web developers to access the Microsoft Stack similar to the BizSpark program.
It is called Website Spark. VS 2008 Professional Edition and SQL Server 2008 Web Editon are some of the tools available through the program.
Of all things I would probably miss the ability to install extensions. Especially tools like AnkhSVN and TestDriven.NET have grown invaluable to me...
I would seriously consider investing some money in purchasing VS especially if you can get some of that back by using it for jobs.
Maybe switching to Eclipse and Java is an option for you?
EDIT:
By the way, investing a few hundred dollars is common among ex-students. If you were a designer you would probably have to invest $1000 on Adobe software.
You won't be able to have solutions with multiple project types (so no mixed language solutions), or solution folders either.
The main thing that is missing is the ability to build an installer for a solution.
The work-around is to build the installer using some open source installer for .NET, e.g. WiX.
And multi-language solutions are more cumbersome (e.g. mixed C# and VB.NET).
I use the Professional version, but I didn't experience any problems with opening and building my project/solution in the Express Edition.