The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

    Mastodon

  • Twitter Updates

  • My Flickr Stream

    20140508-Delphi-2007--Project-Options--Cannot-Edit-Application-Title-HelpFile-Icon-Theming20140430-Fiddler-Filter-Actions-Button-Run-Filterset-now20140424-VMware-Fusion-6.0.3.-no-reclaimable
    More Photos

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 2,969 other subscribers

Archive for the ‘Visual Studio 2017’ Category

« Previous Entries

VS2017 Community .vsconfig file – Visual Studio Community workload and component IDs | Microsoft Docs

Posted by jpluimers on 2021/03/10

When I need to find out what components match my below installed .vsconfig component IDs for Visual Studio 2017 community edition, I can find them in: [WayBack] Visual Studio Community workload and component IDs | Microsoft Docs: Use workload and component IDs to install Visual Studio by using the command line or to specify as a dependency in a VSIX manifest.

{
    "version": "1.0",
    "components": [
        "Microsoft.VisualStudio.Workload.ManagedDesktop",
        "Microsoft.VisualStudio.Workload.NativeDesktop",
        "Microsoft.VisualStudio.Workload.Universal",
        "Microsoft.VisualStudio.Workload.NetWeb",
        "Microsoft.VisualStudio.Workload.Azure",
        "Microsoft.VisualStudio.Workload.Python",
        "Microsoft.VisualStudio.Workload.Node",
        "Microsoft.VisualStudio.Workload.Office",
        "Microsoft.VisualStudio.Workload.NetCrossPlat",
        "Microsoft.VisualStudio.Workload.VisualStudioExtension",
        "Microsoft.VisualStudio.Workload.NativeCrossPlat",
        "Microsoft.VisualStudio.Workload.NetCoreTools",
        "microsoft.net.componentgroup.targetingpacks.common",
        "microsoft.visualstudio.component.entityframework",
        "microsoft.visualstudio.component.debugger.justintime",
        "microsoft.visualstudio.component.vc.diagnostictools",
        "microsoft.visualstudio.component.vc.cmake.project",
        "microsoft.visualstudio.component.vc.atl",
        "microsoft.visualstudio.component.vc.testadapterforboosttest",
        "microsoft.visualstudio.component.vc.testadapterforgoogletest",
        "microsoft.visualstudio.componentgroup.web.cloudtools",
        "microsoft.visualstudio.component.aspnet45",
        "microsoft.component.azure.datalake.tools",
        "microsoft.visualstudio.componentgroup.azure.resourcemanager.tools",
        "microsoft.visualstudio.componentgroup.azure.cloudservices",
        "microsoft.visualstudio.component.azure.mobileappssdk",
        "microsoft.visualstudio.component.azure.servicefabric.tools",
        "microsoft.component.cookiecuttertools",
        "microsoft.component.pythontools.web",
        "component.cpython3.x64",
        "microsoft.visualstudio.component.teamoffice",
        "component.google.android.emulator.api27",
        "component.linux.cmake"
    ]
}

This comes in very useful when installing Visual Studio 2017 through chocolatey:

chocolatey install -yes visualstudio2017community
:: "Microsoft.VisualStudio.Workload.ManagedDesktop", 
chocolatey install -yes visualstudio2017-workload-manageddesktop
:: "Microsoft.VisualStudio.Workload.NativeDesktop", 
chocolatey install -yes visualstudio2017-workload-nativedesktop
:: "Microsoft.VisualStudio.Workload.Universal", 
chocolatey install -yes visualstudio2017-workload-universal
:: "Microsoft.VisualStudio.Workload.NetWeb", 
chocolatey install -yes visualstudio2017-workload-netweb
:: "Microsoft.VisualStudio.Workload.Azure", 
chocolatey install -yes visualstudio2017-workload-azure
:: "Microsoft.VisualStudio.Workload.Python", 
chocolatey install -yes visualstudio2017-workload-python
:: "Microsoft.VisualStudio.Workload.Node", 
chocolatey install -yes visualstudio2017-workload-node
:: "Microsoft.VisualStudio.Workload.Office", 
chocolatey install -yes visualstudio2017-workload-office
:: "Microsoft.VisualStudio.Workload.NetCrossPlat", 
chocolatey install -yes visualstudio2017-workload-netcrossplat
:: "Microsoft.VisualStudio.Workload.VisualStudioExtension", 
chocolatey install -yes visualstudio2017-workload-visualstudioextension
:: "Microsoft.VisualStudio.Workload.NativeCrossPlat", 
chocolatey install -yes visualstudio2017-workload-nativecrossplat
:: "Microsoft.VisualStudio.Workload.NetCoreTools", 
chocolatey install -yes visualstudio2017-workload-netcoretools

Visual Studio 2017 related Packages I still need to research from [WayBack] GitHub – jberezanski/ChocolateyPackages: Chocolatey packages maintained by me:

–jeroen

Read the rest of this entry »

Posted in .NET, Development, Software Development, Visual Studio 2017, Visual Studio and tools | Leave a Comment »

emulation – How to safely remove/uninstall Android Virtual Device .img files added by Visual Studio Emulator for Android – Stack Overflow

Posted by jpluimers on 2020/02/26

Me at [WayBack] emulation – How to safely remove/uninstall Android Virtual Device .img files added by Visual Studio Emulator for Android – Stack Overflow:

Since after uninstalling the “Visual Studio Emulator for Android” component, you cannot get to the “AVD Manager” any more, you have to manually delete this directory:

%LocalAppData%\Microsoft\VisualStudioEmulator

This works for both Visual Studio 2017 and Visual Studio 2015.

In addition, you might want to run “AppWiz.cpl“, then remove “Android SDK Tools”, which is also not automatically removed by the Visual Studio installer (at least not in Visual Studio 2015).

This will get rid of the multi-gigabyte folder %ProgramFiles(x86)%\Android\android-sdk\

If you still need Android emulation, read these:

–jeroen

Posted in .NET, Development, Software Development, Visual Studio 2015, Visual Studio 2017, Visual Studio and tools | Leave a Comment »

NuGet: migrate from packages.config to PackageReference with 3 clicks

Posted by jpluimers on 2020/02/19

Since I often forget to cleanup some bits of a migration: [WayBack] Migrate to PackageReference with 3 clicks:

Related:

–jeroen

Posted in .NET, Development, Software Development, Visual Studio 2015, Visual Studio 2017, Visual Studio and tools | Leave a Comment »

No, Visual Studio Community 2017 is not a 30 day trial – via Stack Overflow

Posted by jpluimers on 2019/04/30

Visual Studio Community 2017 needs a license renewal every ~30 days with a Microsoft account: [WayBack] Visual Studio Community 2017 is a 30 day trial? – Stack Overflow.

This means it is not a trial, but it does not a Microsoft account, and communicate with it every ~30 days which you can get at [WayBack] Microsoft account | Sign In or Create Your Account Today.

Messages you can get:

  • “We could not download a license. Please check your network connection or proxy settings” – meaning: sign in with a Microsoft account by clicking “Add an account…”
  • “We could not download a license, Please ensure your accounts are authenticated.” – meaning you have to click “Reenter your credentials”

–jeroen

Posted in .NET, Development, Software Development, Visual Studio 2017, Visual Studio and tools | Leave a Comment »

from a WSDL import: empty “Reference.cs” – Google Search

Posted by jpluimers on 2019/01/10

A search for empty “Reference.cs” – Google Search seems to indicate this happens with referenced types that – despite turning off that option – from the Visual Studio 2017 IDE sometimes results in an empty Reference.cs.

My solution: import in an empty project, then move the reference to the existing project and add it.

[WayBack] c# – Sometimes adding a WCF Service Reference generates an empty reference.cs – Stack Overflow

–jeroen

Posted in .NET, C#, Development, Software Development, Visual Studio 2015, Visual Studio 2017, Visual Studio and tools | Leave a Comment »

« Previous Entries
 
%d bloggers like this: