Wiki Home

Visual Studio Net


Namespace: WIN_COM_API
Category Needs Refactoring

WOW, this is some really old information. I think this topic can be deleted or some of it refactored to the What Does Dot NETMean To The VFP Developer

from CNet: http://news.cnet.com/news/0-1003-200-2239735.html?tag=st.ne.1003.saslnk.saseml
July 11, 2000

"Today, Microsoft distributed a test version of the next release of its development tools, called Visual Studio.Net, to more than 6,000 attendees here. The tools package includes updates to Visual Basic, Visual C++ and Visual FoxPro tools, and includes the first version of C#, a new tool announced last month. As first reported by CNET News.com, C# is a Java-like software programming language intended to simplify the building of Web services using Microsoft software."
Alex Feldstein
At the September 2000 VBITS in Orlando and at the VFP DEVCON 2000 in Miami, Microsoft announced that the beta version of their .NET framework would be available first to Universal MSDN Subscribers and then to conference attendees.
See: VFPDotNet, VBDotNet, Win Forms, VSDotNet Links
How will this affect the VFP community? -- Alex Feldstein

Seems to me it's just more jargon to learn on top of the new technology advances we were already expecting to get in the next version of Visual Studio. Also seems like the additional hype behind this will make VS7 seem like a "must-have" upgrade. Will it have a direct impact on VFP developers specifically? I dont think so, what about everybody else? -- Rox

Rox- I think it won't impact *pure* VFP programmers at all. If, however, you want access to some nice looking features in ASP+, including the ability to use VB, not VB Script, in web pages, you might give it a look.-- Nancy Folsom

I think it will have a huge impact on VFP developers. VFP 7.0 (VFP.Net?) is the most significant FoxPro upgrade since 3.0. The ability to participate in COM+ is huge. The integration into the VS shell is huge. The continued push to n-tier applications...and the added visibility of VFP in this...is huge. Miami is shaping up to be a MUST attend event. -- Craig Berntson

Keep in mind Craig, the integration into the VS is very limited. The primary gain is in the area of debugging COM Components. If you don't develop using COM Components, this will be an unused feature.. -- John Petersen

I'm aware of this, but IMO, it is the first step of integration. John, please note that I am expressing my opinion here...at some future version we'll see VFP fully integrated into the VS shell. Now, for those of us that do develop COM components, this new feature is a godsend. -- Craig Berntson

Actually I think you just hit on a bigger point John, all the advances they are touting in the next version of Visual Studio pretty much all seem to be n-tier or web centric. Thus my original comment above... I dont see a huge impact here on Visual FoxPro Developers, meaning those folks who only buy a license to VFP and do everything in VFP and VFP only. I think rather the huge impact to be had here is for Visual Studio Developers, meaning those folks who have already bridged the use the best tool for the job gap. A lot of the cool new stuff they are now maneuvering to shove down our throats in the near future will hopefully give Visual Studio developers more marketing muscle when competing for jobs against non-microsoft tool developers (Delphi, Java, and Corba implementations etc.) Granted COM+ is big leap in it's own right, but since Microsoft makes it a necessary technology I expect that technology to be useable from whichever Visual Studio tool I choose to work with. If COM+ was not do-able in the next version of VFP, well then Microsoft is shooting itself in the foot so I see this as a moot point in the discussion of how much impact Visual Studio Net will have on the VFP community. Besides, we were promised COM+ technology long before we ever heard this new Visual Studio Net hype. So therefore, the only direct impact I see here for VFP developers is more incentive for folks to get off the fence and learn other tools in the Visual Studio Suite. Personally, I'm figuring the next checkmate move from Microsoft is to eliminate the individual development tool licenses on Visual Studio Net in order to force everyone to buy the whole dang suite < bg > which if that happens, time for folks to pony up the bucks for a MSDN Universal subscription and accept the fact were being assimilated -- Rox
Have you not heard, VFP is a JV language..< bg >...
Here is the link http://www.devx.com/free/press/2000/meader.asx

There's an old cliche in the motorsports world "If you can't run with the big dogs, stay on the porch." I dont know about everybody else, but being called Junior Varsity pretty much makes it seem to me that VFP is getting porched. -- Rox

Who's that guy in the video anyway?/font>
Patrick Meader, editor and chief of VBPJ (Visual Basic Programmers Journal)/font>
I wouldn't let the comments of a VB dweeb affect one's perception of whether or not VFP is "JV".

He's not a 'vb dweeb' - he's a journalist who understands. ZaneThomas
So, according to what I've read, VFP won't be participating in the new VS integrated IDE? -- Michael Chean
No, it will (to a degree). What has been shown of the VS IDE in the Fox world is the ability to create a VFP middle-tier COM component from the VS IDE.
From O'Reilly news: Microsoft .NET vs. J2EE: How Do They Stack Up?
Category Development Tools Category Visual Studio Category DotNet
( Topic last updated: 2004.03.11 06:06:40 PM )