![]() ![]() Which lets you specify what file is opened. ![]() For script and template pages a special page directive allows you to specify what file should be opened - notice the highlight in the code file above: Web Control Pages automatically open the code behind file. Note Web Connection also supports opening Code behind files using the Web Connection Visual Studio Addin: I've been using Sublime for years because it fires up quickly, but now I may stick with the built in editor simply for the fact that everything is one place. Once done double clicking opens the file in the specified editor. You can map PRG files there to whatever editor you like including the VFP IDE. option to specify a default editor to open files with. If you want a different editor for your PRG files - like Sublime text as I've done for years - you can use the Open With. Other Editors with Web Connection?įWIW, you don't have to use Visual Studio or FoxPro either. ![]() There's no auto-complete support, so you may still want to use the Web Connection add-in to explicitly open FoxPro files in the FoxPro editor. Keep in mind the features are limited to syntax coloring. It's also useful for checking out generated script template PRG files while debugging code and you can also open Process class files (manually) in the editor and see your process class code side by side with a template. If you're Web Control Pages and you keep your PRG files with the script page file, the two files live side by side and you can edit them. This works great when working with Web Connection, so that you can quickly open PRG files and edit them in-place. ![]() It's nice to have native support for FoxPro right in Visual Studio, so you can open and edit FoxPro files right from the Visual Studio project. You'll also want to install the File Icons extension to show appropriate icons for your FoxPro files: Or use the Visual Studio Extension Manager to add it directly from within Visual Studio. You can find out more and install the extension from here: Keep in mind this basic syntax coloring support, not a full featured editor with auto-complete. Thanks to Matt Slay who a while back created a Sublime Text FoxPro language extension, Mads was able to add FoxPro as a language to the extension language pack.Įnd result: You can now view and edit FoxPro files with syntax coloring in Visual Studio natively. Mads is a a Program Manager on the Visual Studio Tools team and the prime driver behind extensions for ASP.NET tooling and he has created a cool extension that can take existing Textmate style syntax files and render them as syntax highlighted documents. Visual Studio 2015 now has support for FoxPro files by way of a very cool add-in from Mads Kristensen. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |