What would be the most frictionless workflow for working with NuGet and Visual Studio 2005? Is this at all possible? I understand that the plugin is only available for Visual Studio 2010, but there is still the package manager console wich seems to be nothing more than powershell. Can I run the console without Visual Studio and can the console download and integrate packages into visual studio 2005 projects? If so, how is this done?
Scott Hanselman blogged about adding NuGet "support" to Visual Studio 2008. You can probably adapt this slightly to work in Visual Studio 2005 too, though of course you won't get the same experience as in Visual Studio 2010.
Well, not really. A better title would be "How to Cobble Together
NuGet Support for Visual Studio 2008 with External Tools and a
Prayer." The point is, there are lots of folks using Visual Studio
2008 who would like NuGet support. I'm exploring this area and there's
a half-dozen ways to make it happen, some difficult and some less so.
The idea would be to enable some things with minimal effort. It'll be
interesting to see if there are folks in the community who think this
is important enough to actually make it happen. Of course, the easiest
thing is to just use 2010 as it sill supports .NET 2.0, 3.0, 3.5, and
4, but not everyone can upgrade.
Someone could:
Backport the existing NuGet Package References dialog to 2008 using
that version's native extensions (not VSiX)
Create MEF (Managed
Extensibility Framework) plugins for the nuget.exe command-line to
update the references in a vbproj or csproj
Use PowerShell scripts and
batch files to get the most basic stuff working (get a package and
update references.)
Maybe write a shim to get DTE automation
working...
But that's coulds and maybes. Let's talk about the MacGyver
solution. more ยป
Related
I'm looking to create a very simple UI plugin for Windows Media Player, similar to this: https://obsproject.com/forum/resources/windows-media-player-title-artist-text-output-ticker.402/, but with the ability to choose the path and name of the text file.
I haven't been able to find any answers to WMP Plugin development questions on here since 2013, and the last actual answer give was for Visual Studio 2008. I'm now using Visual Studio 2019, so almost all of the tutorials, guides, and FAQs are massively out of date.
I've been following the setup guide here: https://learn.microsoft.com/en-us/previous-versions//aa969437(v=vs.85)?redirectedfrom=MSDN
After a few hours, I've finally been able to install the Windows 7.1 SDK by deleting all my C++ 2010 redistributables, and temporarily rolling back my .NET Framework 4 version to RTM. I now have wmpwiz.ico, wmpwiz.vsdir, and wmpwiz.vsz.
The interal version of VS2019 is 16.0, so I've edited my wmpwiz.vsz file to read:
VSWIZARD 7.0
Wizard=VsWizard.16.0
Param="WIZARD_NAME = Windows Media Player Plug-in Wizard"
Param="ABSOLUTE_PATH = C:\Program Files\Microsoft SDKs\Windows\v7.1\Samples\multimedia\WMP\Wizards\wmpwiz"
Param="FALLBACK_LCID = 1033"
and I've placed the three files into %UserProfile%\Documents\Visual Studio 2019\Templates\ProjectTemplates\Visual C++ Project\, but nothing shows up in the Start New Project window.
Obviously, I'm using technology that hasn't been touched for over a decade, so I don't know if this approach will even work anymore. Are there any modern guides on how to do this, or would it be quicker and easier to try to dig out my old VS2005 install disks, and hope they're not too scratched?
If this SDK Sample has been depreciated with age, are there any other wizards available that can be used for WMP plugin development? Preferably using C#, as I'm a .NET programmer, but I'm happy to trawl through C++ if I absolutely have to.
Thanks for any help you can give.
I just came to know about Visual Studio Code. I would like to know, can I replace Visual Studio for all .NET development related work?
Can I save my cost of Visual Studio licensing?
What is there in Visual Studio which is not there in Visual Studio Code?
This question already has an answer here and here.
The list of differences is huge.
Visual Studio Code is a source code editor developed by Microsoft for Windows, Linux and macOS,
with emphasis in just writing the code instead of dealing with
debugging, compiling, testing, refactoring, and all the other things
that make Visual Studio great.
The people using Visual Studio Code will probably be those on a Mac
who will just deal with client-side technologies (HTML/JS/CSS) and do
not want to install Windows in order to do that.
People using Windows and developing C#, F# or VB will continue to use
Visual Studio 2015.
Also the difference is that .NET has been split into two: .NET Core
(Mac/Linux/Windows) .NET Framework (Windows only) All native user
interface technologies (Windows Presentation Foundation, Windows
Forms, etc) are part of the framework, not the core.
Also, Visual Studio tends to be oriented around Projects & Solutions.
Projects have a large amount of scaffolding (pre-generated starting
templates) and features.
VS Code looks to be presently oriented around files, as a glorified
text editor, and no project scaffolding exists.
Source : MSDN forum and quora
I've been developing on Visual Studio, and here comes Visual Studio Code which is described as a source code editor that supports multiple platforms. For me, I find it promising considering it's a lightweight editor compared to Visual Studio.
Since Visual Studio Code is still a baby, is it safe to say as time passes by and this baby becomes mature, this will be the new Visual Studio considering it can run on multiple platform?
Does Visual Studio Code has a roadmap on the upcoming features?
Visual Studio Code will not replace the regular Visual Studio, if that's what you're asking. VSCode is intended to be a very lightweight, code-focused IDE. There are a plethora of features present in Visual Studio that I don't expect we'll ever see in VSCode simply because they are not within the scope of the project. For example, I don't think you'll ever see the designer in VSCode, which is something you would sorely miss if you were developing a WPF or WinForms application.
Right now VSCode seems to be mostly targeting web application developers using ASP.NET 5 and node.js.
As for what's ahead for VSCode, I'm not sure if a roadmap has been laid out anywhere but I do know that a plugin/extension system is in the works, along with ES6/7 support and a few other things.
If you want to follow the development of VSCode, check out their blog, Twitter, and UserVoice.
Does no such plugin exist?
So to be clear, I realize that RedGate has their own SSMS SCC app, and I realize that VSS2k5 will integrate in. I'm looking to stay with Hg as that's where my source already is, and I'ld like to find something that my team can stay consistent with on their tools.
As is, I guess I'm going to have to just run it through TortoiseHg and a folder with manual maintenance. Which isn't terrible, but naturally it would be nicer if there was an app pre-existing that I could consume.
And no, I don't have the time or inclination to write one myself. Not before Summer 2011.
Thoughts or ideas?
There are two versions of HgScc plugin:
HgScc - uses old MS SCCI API, works with MS VS2005/2008/2010 and with some third party IDEs. Last version of this plugin was released in 2008. It is not actively developed anymore, because MS SCCI API is very limiting and does not allow a tight integration with Visual Studio.
HgSccPackage - uses MS SCC Package, works only with MS VS2008/2010. This version of plugin currently in active development.
To get the first version of HgScc follow the instructions here:
MSSCCI compliant Mercurial client
Red Gate SQL Source Control is looking into supporting Mercurial in a future version, http://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/803713-mercurial-support-as-source-control-system.
SQL Server 2012 (Denali) is using the Visual Studio 2010 Shell as the basis for the new Management Studio. I haven't tried it yet but I am hoping that tools such as VisualHg will work in Sql Server 2012. I will update this post after I get on my laptop that has the 2012 SQL Management Studio installed.
Have you tried hgscc? I know it integrates with Visual Studio, but I haven't tried it with SSM
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.