#vs2019

[s1ilence]

[infinetsoft]

One or more projects in the solution were not loaded correctly in Visual...

[itsaloyd]

Error DEP6957: Failed to connect to device '127.0.0.1' using Universal Authentication

Try another usb cable. Did you use the one which comes with the Hololens?

[itsaloyd]

Error : Out of memory

If for no reason, your VS2019 solution doesn’t seems to build anymore, try to restart your computer even if everything looks alright in the task manager and that you have plenty of memory.

[keyboardp]

Choose your Own Shortcut for Quick Unity3D Doc Access Within VS2019

If you’re using Visual Studio 2019, there’s a handy shortcut you can use to quickly jump to the documentation of any Unity Engine API object or method. You click on the object, press CTRL + SHIFT + M and then press CTRL + H. However, I find this is a bit too fiddly so I found a way to quickly change it to a shortcut I prefer.

Simply go to Tools...Options...Keyboard (on the left)...

Search for “unity” in the “Show commands containing” textbox

Select Help.UnityAPIReference

Click in the Press shortcut keys textbox

Press the key combination you’d like to use and click “Assign”. I preferred CTRL+SHIFT+ALT+H but you can choose what you like (just be careful not to choose a combination that overrides an existing keyboard shortcut)

That’s it! Click on your object in your code, press the combination you selected, and VS will open up the documentation without you having to leave the IDE.

If the gif below is too small, click here for a larger version

[msicc]

How to work around IDE freezes in Visual Studio 2019 when switching between Build configurations

I just blogged: How to work around IDE freezes in #VisualStudio 2019 when switching between Build configurations #VS2019

After a lot of project unloading, deleting our custom configurations back and forth and project file modifications, we finally found a workaround to continue our work by browsing other/similar issues to ours in the VS feedback forums. The freeze of the solution is caused by a feature that is meant to fasten up solution loading: parallel project initialization.

It seems to be an issue that…

View On WordPress

[ryadel]

Visual Studio - parameter instance with value null when opening XSD files

If you've stumbled upon this post it most likely means you're having issues while trying to open XSD files from Visual Studio 2017 or 2019. More specifically, this problem often happens when you try to open a .xsd file of a rather old project, originally created using the ASP.NET Framework 2.0, 3.5 or so on and then upgraded to ASP.NET 4.x later on. The error message presented by the Visual Studio GUI is the following: Value cannot be null. Parameter name: instance And here's the stacktrace: Hide Call Stack at System.ComponentModel.TypeDescriptor.AddAttributes(Object instance, Attribute attributes) at Microsoft.VisualStudio.Design.VSDesignSurface.CreateDesigner(IComponent component, Boolean rootDesigner) at System.ComponentModel.Design.DesignerHost.AddToContainerPostProcess(IComponent component, String name, IContainer containerToAddTo) at System.ComponentModel.Design.DesignerHost.PerformAdd(IComponent component, String name) at System.ComponentModel.Design.DesignerHost.Add(IComponent component, String name) at System.ComponentModel.Container.Add(IComponent component) at Microsoft.VSDesigner.DataSource.Designer.DataSourceDesignerLoader.HandleLoad(IDesignerSerializationManager serializationManager) at Microsoft.VSDesigner.DesignerFramework.BaseDesignerLoader.PerformLoad(IDesignerSerializationManager serializationManager) at Microsoft.VSDesigner.DesignerFramework.BaseDesignerLoader.Microsoft.VisualStudio.TextManager.Interop.IVsTextBufferDataEvents.OnLoadCompleted(Int32 fReload) This seems to be .net 3.5 specific as I opened another project that's 4.0 and its .xsd opened in designer fine. This is a screenshot of the error, as shown by the Visual Studio xsd design view/mode:

The Fix

At the time of writing (July 2019) there are at least two open issues created to address this problem on the Visual Studio Developer Community website: #26937 - DataSet fails to open in designer #54432 - Opening Dataset xsd's Throws Designer Error Despite these feedbacks, there are no official answers - or fixes - released by Microsoft so far. Luckily enough I was able to find a workaround by mixing two different suggestions taken from two treads on MS Development Network and StackOverflow. The workaround I found works that way: Open the Project (or Website) Property Page. Locate the section where you can choose the .NET Framework version (Start Options -> Build for most project types). If your project is using a .NET Framework lower than 4.7.2, set it to 4.7.2 (in case you don't have it installed, you might have to download it and restart Visual Studio afterwards). If your project is using the .NET Framework 4.7.2, downgrade it to 4.6.1 (again, if you don't have it download it and restart Visual Studio). This should permanently fix your problem and let you open the XSD files in design mode.   Read the full article

[cheerchain]

Visual Studio Professional 2019 商業授權下載版(五套,永久授權版, ESD)-適用於個人開發人員或小型小組的專業開發人員工具及服務! Visual Studio Professional 2019-適用於個人開發人員或小型小組的專業開發人員工具及服務。以任何 App、任何語言、任何平台為目標的整合式開發環境! #IDE #VS2019 #CodeLens #Agile #專案規劃 #Azure #Pluralsight https://www.pcstore.com.tw/cheerchain/M54625826.htm