Microsoft on Tuesday will offer a glimpse at future versions of its Visual Studio.Net development tools and highlight a number of additions to the product line. In the meantime, support grows for .Net: A number of Microsoft partners will announce at VSLive products targeted at Microsoft’s .Net. Also, Microsoft Corp. on Monday renamed its XDocs application to InfoPath, but declined to say whether this information-gathering tool would ship as part of Office 11, the code name for the next version of Office, or if it would be sold as a stand-alone product.
Microsoft Peeks at Visual Studio.Net’s Future
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
I read somewhere that they are going to make VC++ ‘visual’ like VB and VC# ?
They’re adding Winforms support to the IDE for Managed C++. Before you could still use Winforms with Managed C++, but not with the GUI perks in the IDE as with C#, etc. I think that’s what you’re referring to.
http://www.microsoft.com/windowsserver2003/evaluation/overview/dotn…
I was reading about 2003 server (formerly .NET server or something) and caught this quote.
“To reduce the attack surface, IIS 6.0 is not installed by default on Windows Server 2003 —administrators must explicitly select and install it. Once installed, IIS 6.0 is configured in a locked-down state in which it can only serve static content by default.”
It’s nice to see them start to come around.
This headline should read ‘Microsoft Offers Peek at Visual Studio.Net’s Future’ or ‘Microsoft Partially Reveals Visual Studio.Net’s Future’.
Is anyone here a little tired on what version numbers Microsoft gives to their products? From Office 6 to Office 95 to Office XP. Pick one. I would go for the numbering. Or the years. But “XP”? Please, spare me. The same goes for Windows. I much much prefer having Windows XP as Windows 2002.
The next verion is going to be Office 11, the odds of the version after that being 12 are slim. If it is, you will probably see is as XII or something.
OSNews may have a few grammatical errors here and there, but they have a LONG way to go to catch up to /. 🙂