Visual Studio 2015?

Hello all,

We have been developing a product in Visual Studio 2012 for a while now. Yesterday we decided to task one of my colleagues, a junior person who has shown a lot of potential, with some work to get him into the development space where, I think, he can make a real contribution over time. Anyway, that aside. We went looking for VS2012 and couldn't find it anywhere in our MSDN subscription, only a VS2012 Update 5, but the update is no use without the original install source.

Of course we have access to VS2015, and in normal circumstances I am usually quite keen to stay current. But I have had a VERY bad experience with our last upgrade from VS2010 to VS2012. We had created Setup projects using the InstallShield software that came with VS2010, only to find that this product had been pulled from VS2012 and we had to scramble to find alternative solutions to the problem. It was unnecessary additional work.

So I'm reluctant to move to VS2015. What nasty surprises will we be presented with then? What can you, experts, tell me to either allay my fears or warn me off making this move?
LVL 4
WernerVonBraunAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Mr KnackeredCommented:
Moving from VS2013 to VS2105 was painless from my side. I did however have an issue with the .NET framework 4.6 and ended up using VS2015 and targeting the 4.5 framework. The issue was down to multilingual resources files with WPF and C#. For some reason with the 4.6 framework if you open a windows and set the culture to language "A" everything was fine but if you opened another window the culture went back to the default which is not the behaviour in previous frameworks. I found resetting the culture on the new window didn't always work correctly thereafter.

So far apart from the framework issue I have not had any problems with VS 2015. I also like very much the new references feature which shows next to each code block the number of times its called and where from, very useful indeed. The new performance monitoring is also very useful.

I had the same issue as you when upgrading with deployment projects not being supported in place of install shield very basic edition on the earlier move from 2010 to 2012. I ended up having to build a new installer and chose Advanced Installer over install shield.

I would just go with VS2015 bite the bullet and use the new technology. You will have to do it at some point so it may as well be now. There could be issues outside of WPF and C# that I wouldn't be aware of but I use it all day long and have not had any major problems or found anything apart from the problem above.

Hope this helps

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
HuaMin ChenProblem resolverCommented:
Hi,
By VS 2015, you can open all your previous VS 2012 project, under 64-bit OS. But using VS 2015, it means you at least have to deploy the projects to Win 2008 server (no more Win 2003 server).
it_saigeDeveloperCommented:
@HuaMinChen - could you elaborate a bit.  It appears as if you are stating that you can no longer build 32-bit applications with VS2015.  Which is simply not the case, you can build both 32-bit and 64-bit applications with VS2015 which means that you could still deploy projects on Server 2003 (so long as the projects target .NET 4 or lower).

That being said, even if you could only build and deploy 64-bit applications; you could still deploy your application to a Windows 2003 Server  (which was offered in a 64-bit version) as long as your project targets .NET 4 or lower.

-saige-
Learn SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

WernerVonBraunAuthor Commented:
Yes, that sounds reasonable, it_saige. In any case, it's not a situation that will arise in our case. But good to know.
HuaMin ChenProblem resolverCommented:
I mean VS 2015 will perform very well on 64-bit platforms like Win 8.1, Win 10, Win 2008/2012 server. But we can still build 32-bit application by that.
WernerVonBraunAuthor Commented:
Thanks all
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
.NET Programming

From novice to tech pro — start learning today.