Articles filed in category 'VFP and .NET'

Part 3, The User Interface and the Rating Web ServiceWe are finally going to get our feet wet in Visual Studio .NET and start writing some real code! In this article, we're going to focus on two areas of the ACME application. First, we will talk about the user interface and how it's implemented in ASP.NET ? along with a few problems we overcame by utilizing the powerful object-oriented features of .NET. Next, we'll write a web service in Visual Basic .NET to rate polic...ies based on their class codes. To demonstrate that web services can be used in a variety of ways, we'll consume the web service in both .NET and Visual FoxPro 7.See More

The .NET Framework presents exciting new opportunities for developers. By now, you may have heard that .NET represents a departure from COM, the focal point of Windows development for the past several years. Because of the investments in COM, it is quite likely you will want to implement COM in VS .NET. Conversely, the .NET Framework has a number of nice features that you will want to implement in COM-based applications. This article illustrates how COM and the .NET Framework can work together.

This article highlights some of the new toolkits and components coming out of Redmond for COM Interop.The Interop Forms Toolkit, the Interop UserControl Prototype, and the techniques used in Sedna’s NET4COM allow Visual FoxPro developers to incorporate .NET components into their applications.

The series of test conducted here are based on the "String Processing with VFP" article published in the Spring 2000 issue of CoDe Magazine.

How we spent our family winter vacation: at a Visual FoxPro Conference in Hawaii!

A practical look at what’s involved in converting your Visual FoxPro (VFP) applications to Visual Studio and SQL Server. Let me say up front that I am a long-time FoxPro developer and that I love VFP. I also love .NET and SQL Server and I’ve headed up and participated in many conversions. Most of the conversions I’ve worked on were not driven by technical necessity, but by customer demand that software be built with .NET and SQL Server. Whatever the reason, conversion fr...om VFP to .NET is a significant undertaking.See More

Whenever more than one person works on a software development project, introducing some process to coordinate the activities of the team members is a priority.The larger the team, the harder it is to manage. To meet this need, Microsoft created Visual Studio Team System (VSTS). VSTS is a state-of-the-art Software Development Life Cycle tool suite that is tightly integrated into Microsoft Visual Studio 2005. VSTS provides deep support for .NET projects; however, whenever ...a software solution includes components developed on a platform other than .NET, such as Microsoft Visual FoxPro (VFP), VSTS loses some of its value because the projects aren’t integrated into VSTS. Leveraging the extensibility features of VSTS and VFP, this article will help you integrate VFP projects into VSTS team projects enabling your team to apply a comprehensive process to your entire software development effort.See More

At PDC 2005, Microsoft introduced brand new technology known as LINQ, which stands for “Language Integrated Query.”The feature-set hiding behind this acronym is truly mind-boggling and worthy of a lot of attention. In short, LINQ introduces a query language similar to SQL Server’s T-SQL, in C# and VB.NET. Imagine that you could issue something like a “select * from customers” statement within C# or VB.NET. This sounds somewhat intriguing, but it doesn’t begin to communicate the power of LINQ.

String processing is an important aspect of today's applications.Web applications in particular, rely heavily on string transformations and special formatting of data, as well as generating strings for output to the Web dynamically in the form of HTML, XML or even binary data. In this article, Steve demonstrates and compares performance of some of the powerful string functions in Visual FoxPro.

When Visual FoxPro developers take the plunge to learn .NET, the most common reaction is, “I could do such-and-such, this-and-that in VFP-how can I do it in .NET?” This special edition of The Baker’s Dozen will offer solutions for many of the typical challenges that VFP developers face when tackling .NET. I’ll start by covering .NET solution and project structures and an overview of the .NET Framework, and I’ll spend time showing how to use .NET reflection to do some of ...the things that VFP developers could accomplish with macro-expansion. Then I’ll cover different .NET features such as Generics, ASP.NET 2.0, and I’ll show how to create a reusable data access component. Finally, I’ll build the architecture for a set of reusable data maintenance classes in .NET.See More

.Net is a maturing platform. The first .NET alphas and betas went to a selected group of people years and years ago. At this point, we are approaching the third major installment of Visual Studio .NET (now called "Visual Studio 2005"). Surely at this point, nobody has to explain what .NET and the Managed Platform is. Or do we?

Visual FoxPro’s (VFP) Data Manipulation Language (DML) is one of VFP’s most compelling features. It is also the most obvious feature VFP developers miss in .NET languages such as C# and Visual Basic. However, Language Integrated Query (LINQ), a new query language for .NET developers is a new feature in the upcoming releases of C# 3.and Visual Basic 9.0 that addresses these shortcomings.

New to Sedna, Visual FoxPro emulates the My namespace first introduced in Visual Basic 2005.The My namespace makes .NET Framework classes more discoverable and allows you to write less code. Sedna, the next version of Visual FoxPro (VFP), includes a My namespace as well, for the same reasons. In this article, I’ll look at how Sedna implements My.

The Data Explorer introduced in VFP 9.0 allows developers to work with different types of data from diverse data sources independent of specific projects.The Sedna update extends this already powerful and productive tool.

Visual Studio .NET offers a rich tool set, but anyone who has ever used Visual FoxPro will soon notice that many of their favorite features are not available. However, a new set of public domain classes can add these functions to both Visual Basic .NET and C#.

Web services with Visual FoxPro (VFP) have never been easy. The most common Web service tool for FoxPro is the SOAP Toolkit, which has been discontinued and which had a host of problems when dealing with complex types passed over Web Services. In this article I’ll show how you can leverage the powerful Web service features of .NET and the new Windows Communication Foundation in your FoxPro application through COM Interop.

You can use ClickOnce to revolutionize how you install and update Visual FoxPro (VFP) applications. A dream come true, ClickOnce can put a stop to many of the deployment nightmares associated with distributing applications.