I was wondering if there was a more efficient way of managing betas in visual studio.

Let me provide an example of my thinking.

Lets say i have an application, it's version 1.8.4.

But i want to go ahead and work on a beta, version 2.0.

Version 2.0 has some drastic new features in it that will require testing, but i don't want to loose the 1.8.4 code data.

I want to be able to work up from 1.8.4 and create a 2.0, but keep kind of a separate version to keep the 1.8.4 code together, because if and when bugs/problems emerge from 1.8.4, i don't want to present my users with the whole new 2.0. I want to be able to release 1.8.5 to fix the current bugs.

Is there a better way to do this without creating a new project entirely?

Instead of myapp 1.8.4, myapp 1.8.5, myapp 2.0 beta projects.

How should i go about organizing this?

Thanks.