I recently installed Microsoft new "Visual Studio Code" on Windows. The entire setup was quick and nice. What technology is that? Is it clickonce? It was smooth and quick
It's using Squirrel to create a self extracting zip archive containing a nuget package. Squirrel only supports per-user installation and because of that it doesn't impress me.
Enterprises want per-machine installations with auto-update disabled so that change can be centrally managed. Technologies like Click Once and Squirrel just ignore this and do limited things in the per-user context with auto updates enabled. Two different animals.
Related
Is there an easy way to backup the installed extensions list in VS (2017), so that when I install the machine anew I can easily install my regular extensions at once?
Note: I've found this question that asks an identical question to my own, except it targets VS Code, whereas my question is about Visual Studio for Windows.
Roaming Extension Manager is built in Visual Studio 2017:
The Roaming Extension Manager helps you keep track of all your
favorite extensions across all of your development environments.
Roaming your extensions keeps track of the extensions you have
installed by creating a synchronized list in the cloud.
See also https://devblogs.microsoft.com/visualstudio/roaming-extension-manager-control-and-consistency-down-to-the-last-extension/
Re-visiting this for Visual Studio 2019, you can use this extension to import/export your extensions: https://marketplace.visualstudio.com/items?itemName=MadsKristensen.ExtensionManager2019
Just installed redgate's VS integration for db development. Can't seem to navigate to procedures called from within other procedures (eg ctrl-click to get there).
This would seem a no brainer feature. Am I missing something?
Thanks
Tim
The edit windows do not have the same go-to capabilities as programming code (C#, VB) windows. I added an enhancement request to the Red Gate bug tracker.
Red Gate Software make a few distinct, separate extensions to the Visual Studio development environment for managing databases. SQL Connect is for source controlling databases, and SQL Prompt adds intellisense to database projects. If you can say which extension and how you believe it's supposed to behave, perhaps I can offer some advice.
For source control we currently use Team Coherence 7.1.3.25, which has been working great under a few different editions of Visual Studio, the latest being VS2008. We are migrating to VS2010 and I am not sure how to get TC to work with it. Do we need to make the switch to TFS, or is there an option to get TC to work with VS 2010?
And here is the answer:
"Make sure that you check the 'SCC API' support option in the IDE Installation tool (IDEInst.exe in the installation folder).
When you next run VS, you should then have the 'Source Control' option under the File menu.
If you need more information, let me know.
Regards
Ewan McNab
Quality Software Components Ltd
Version Control with Team Coherence"
I found a great article on integrating different diff and merge tools with Visual Studio 2005 and 2008: http://blogs.msdn.com/jmanning/articles/535573.aspx.
Does anyone know how I might integrate a tool like KDiff3 in the same way with Visual Studio.Net 2003? I would like to have KDiff3 be the default diff tool when I use the "Compare Versions..." menu item in the Solution Explorer.
For our source control, we're using Team System 2005, using the msscci provider to integrate.
What source control system are you using?
With certain systems you can specify what diff tool you'd like to use. Perforce has this...and I believe VisualSVN lets you choose what diff tool as well.
If you've got VSS...I think you're out of luck...
Thank you for that question and comment. It got me to realize the compare was coming from VS2005, even though I'm using VS2003, because the msscci provider I'm using for source control integration is the VS2005 version.
So, by going into VS2005 and using "Configure User Tools...", it forces 2003 to use the same tools.
I know that Devart CodeCompare shows good results on the integration with Visual Studio. But I don't know what VS versions are compatible with CodeCompare.
I like to keep my source files on a USB drive for the portability. To date I have been using Visual SourceSafe for this purpose. What is a good alternative to VSS that fulfils these criteria:
Entire database can be held on a USB "pen" drive
Code / documentation duplicated on local drives
Does not require a central server
Easy to backup and restore using standard backup tools
Integrates with Visual Studio
Has a small footprint
Easy to clean the database and keep small
Compatible with Windows XP, Vista and Vista x64
A good reference on setup would be good too.
I would use SVN (Subversion).
You can use SVN in "file" mode (w/o using the network).
combine this with tortoiseSVN, which integrates to explorer, and you have a nice little portable repository.
For Visual Studio integration, there is the commercial($49) VisualSVN (which I believe is the setup used to develop StackOverflow).
Someone also mentioned AnkhSVN which I haven't used, but some people find it less than satisfying.
Don't use SourceSafe. There's major problems with it. See this:
Article1
Article2
I'd recommend using SubVersion instead.
If you're using Windows, you can use TortoiseSVN.
If you're working on Linux or other Unix variants, try RapidSVN.
Use Subversion. The FSFS style repository will work best as older BDB ones can have issues when moved from computer to computer. With AnkhSVN you'll have full integration with Visual Studio (AnkhSVN 2.x is a source control plugin; older versions still do the job, though).
Bazaar does what you're asking for (in terms of working very well standalone), and there was a 2007 Summer of Code project to build a Visual Studio integration plugin which appears to have produced an at-least-partially-functional product.
Bazaar (and other distributed tools, such as Git, Mercurial, Darcs and the like) are ideal because you can have your repository stored in multiple places (ie. on your pen drive, but also copied up to a server on a regular basis), make changes in one or the other branch (let's say you leave your pen drive at home -- you can build changes against the copy on a remote server, upload them via WebDAV, SFTP, etc, and be able to seamlessly merge them into changes done locally to the pen drive; non-distributed solutions such as Subversion don't have that capability).
There are two common free front-ends Ankhsvn integrates into visual studio
and TortoiseSVN integrates with explorer ( my preference).
There is also sliksvn a self contained svn server for windows.
I'd recommend SubVersion as well - you can find a hosting provider who offers SVN for really cheap, this way your source code is always backed up and available, all you need to keep on your flash drive is SVN client...