I know where you're coming from, because I've had the same problem.
In the visualstudio uservoice link, Mads K. says, "This is fixed in VS11".
So the fix is in Visual Studio 2012, not in VS2010.
https://en.wikipedia.org/wiki/Microsoft_Visual_Studio#Version_history
However, might I suggest another method of attacking the problem?
Completely ignore the .min file.
Completely ignore it, because:
(1) The .min css file, even when we do want to edit it, is a pain to edit. At least that has been my experience.
(2) If you use the Microsoft ASP.NET Web Optimization Framework, you can use bundling and minification, so then there is no need to work with .min files, because the Optimization framework will do the minification for you, even in VS2010 .NET 4.0. Then you can edit the un-minified .css file, and let .NET do the minification for you. It's a win-win from my perspective.
One thing to keep in mind if you should happen to have a bunch of stylesheets with a bunch of rules that you want to bundle into one single .css file are the limitations of Internet Explorer: http://support.microsoft.com/kb/262161.
Some relevant posts:
1. http://kwilson.me.uk/blog/enabling-bundling-and-minification-support-in-a-net-4-application/
2. http://igorzelmanovich.blogspot.com/2012/09/using-aspnet-bundling-and-minification.html
3.
answered 2013-06-07T00:35:20.840