Discussion on:
View:
Show:
I always read these articles hoping for some sense that Microsoft might remember power users. I vaguely recall at one time that power users could customize Microsoft applications with something called "macros" which even progressed to "VBA". But then security issues or excuses arose and Microsoft seemed to stop officially supporting this and instead moved customization to Visual Studio. Unfortunately, Visual Studio is reserved to "real" programmers at many corporations and power users are left to sigh wistfully as Word add-ins no longer function properly.
... and most likely will be for a long, long time. Too many customers have a large investment in macros/VBA for Microsoft to abandon support for it. They just keep cranking up the security controls which makes it harder and harder to access the functionality. For example, in Office 2007 and up, documents with macros even need a different extension to help identify them to users as a potentially damaging item.
J.Ja
J.Ja
I'm not a big fan of TFS. TFS' big advantage is the total integration of the lifecycle and integration with Visual Studio, and other products (like Fog Bugz and Kiln, off the top of my head) provide that as well. When I have a choice, I use Mercurial. But, many shops insist on using TFS, and TFS is part of the Visual Studio family, so I felt that it was important to take a look at the TFS experience. And yes, it is improved, at least from the installation standpoint. But the overall workflow hasn't changed, and the things that I don't really like about TFS... well, they are never going to go away because they are integral to the TFS product.
J.Ja
J.Ja
Looking at the screenshot, it appears that there is no "colour-coding" of items in the tree. Is it harder to see what you're looking for in all grey? It certainly looks that way.
You are correct that there is very little color coding... not just in the Solution Explorer, but in the entire application. Outside of the code editor itself, it is a mix if grey, white, black, and blue (for highlighted items). It does indeed make things harder to see, and is one of the most common criticisms of the Visual Studio 11 experience.
J.Ja
J.Ja
Is it just my imagination or does the VS 2011 Solution Explorer have more of a Mac OS look than a Windows look?
if some thing essential for W7 keep it alive until reach varity VB+Visual studio developer nice more than ASP.net yah.
Thanks
Wisam H.al Bayaa
Thanks
Wisam H.al Bayaa
That is one of the shoddiest "reviews" I've ever seen. You take a product of the complexity of Visual Studio and you review it by saying that you think there is a "red flag" because Visual Studio isn't a Metro style application?
How dumb is that? You have 100% misunderstood what a Metro style application is for and what a desktop application is for. Why do you think the desktop is still there in Windows 8? It's because there are a whole class of applications that we've been using for 25 years which really need a mouse and keyboard. Metro style applications are different, "at a glance" style applications.
Then you note that WP7 support isn't in the product. Of course it will be and it's written up on the public internet here http://windowsteamblog.com/windows_phone/b/wpdev/archive/2012/03/05/windows-8-and-the-windows-phone-sdk.aspx
Don't write any more of this stuff. You're not helping anyone.
How dumb is that? You have 100% misunderstood what a Metro style application is for and what a desktop application is for. Why do you think the desktop is still there in Windows 8? It's because there are a whole class of applications that we've been using for 25 years which really need a mouse and keyboard. Metro style applications are different, "at a glance" style applications.
Then you note that WP7 support isn't in the product. Of course it will be and it's written up on the public internet here http://windowsteamblog.com/windows_phone/b/wpdev/archive/2012/03/05/windows-8-and-the-windows-phone-sdk.aspx
Don't write any more of this stuff. You're not helping anyone.
In case it wasn't clear, this was not meant to be a full-fledged review. It is the initial impressions of someone who is starting to do development with it. I am continuing to write about VS11 as I do work throughout the next few weeks, as you can see from the most recent article that went up yesterday.
I most certainly did NOT misunderstand the differences between Metro and desktop. I have written extensively about the difference a number of times. I have been doing WP7 development for some time. But that does not change the fact that a lot of people have been saying that Metro cannot do "real work", and that Microsoft clearly feels that the legacy desktop model is outdated. Microsoft has made it clear with Windows 8 that the legacy desktop is not something they care to put additional investment in, and they do not seem to feel that it has much of a future; application developers and users alike are rightfully quite concerned that if Microsoft isn't going to care about the legacy desktop, that Metro had better be able to handle complex work. There is simply no reason *at the UI level* why VS11 cannot be a Metro app, but of course, the limited WinRT API would be the real issue (unless, of course, it communicated with a bunch of locally installed services for the things like compile, debug, etc., which is a possibility!). A Metro version of VS11 would go a long way in satisfying those folks. You will also note that I made it VERY clear that even if Microsoft wanted to, a Metro/WinRT version of VS would be an impossibility due to the restrictions in the WinRT API.
Apologies for not knowing 100% the status of the WP7 SDK.
Finally... you may want to think about toning the personal attacks down a bit. I happened to see on another article a similarly nasty comment directed at another TR writer. TechRepublic is generally a civil place, even when there is disagreement. Lately, though, a number of people have come in and started treating it like yet another stinking hole on the Internet for them to vent their rage and frustration and take it out on the folks who work hard to deliver content. If you don't like the article, that's fine. Feel free to disagree and criticize, and I will gladly respond as best I can. But there is no need to trash the writers or the articles themselves. If you feel you can do better, we are always on the lookout for more writers. Instead of taking the easy, negative route and writing a "your article is junk" comment, file to be a writer and try it. I write 2+ articles a week for the last 6 years, it is a guarantee that every one won't be perfect, satisfy everyone, contain every possible fact, or examine every possible angle. You are more than welcome to send me your own review of VS11, and I will see if we can get the editors to post it.
But there is no need for personal attacks or being nasty.
J.Ja
I most certainly did NOT misunderstand the differences between Metro and desktop. I have written extensively about the difference a number of times. I have been doing WP7 development for some time. But that does not change the fact that a lot of people have been saying that Metro cannot do "real work", and that Microsoft clearly feels that the legacy desktop model is outdated. Microsoft has made it clear with Windows 8 that the legacy desktop is not something they care to put additional investment in, and they do not seem to feel that it has much of a future; application developers and users alike are rightfully quite concerned that if Microsoft isn't going to care about the legacy desktop, that Metro had better be able to handle complex work. There is simply no reason *at the UI level* why VS11 cannot be a Metro app, but of course, the limited WinRT API would be the real issue (unless, of course, it communicated with a bunch of locally installed services for the things like compile, debug, etc., which is a possibility!). A Metro version of VS11 would go a long way in satisfying those folks. You will also note that I made it VERY clear that even if Microsoft wanted to, a Metro/WinRT version of VS would be an impossibility due to the restrictions in the WinRT API.
Apologies for not knowing 100% the status of the WP7 SDK.
Finally... you may want to think about toning the personal attacks down a bit. I happened to see on another article a similarly nasty comment directed at another TR writer. TechRepublic is generally a civil place, even when there is disagreement. Lately, though, a number of people have come in and started treating it like yet another stinking hole on the Internet for them to vent their rage and frustration and take it out on the folks who work hard to deliver content. If you don't like the article, that's fine. Feel free to disagree and criticize, and I will gladly respond as best I can. But there is no need to trash the writers or the articles themselves. If you feel you can do better, we are always on the lookout for more writers. Instead of taking the easy, negative route and writing a "your article is junk" comment, file to be a writer and try it. I write 2+ articles a week for the last 6 years, it is a guarantee that every one won't be perfect, satisfy everyone, contain every possible fact, or examine every possible angle. You are more than welcome to send me your own review of VS11, and I will see if we can get the editors to post it.
But there is no need for personal attacks or being nasty.
J.Ja
- Keyboard Shortcuts:
- Prev
- Next
- Toggle
