Oron
Oron
I think I have figured it out. Here is my new minimal vsconfig that works: ``` { "version": "1.0", "components": [ "Microsoft.VisualStudio.Component.Roslyn.Compiler", "Microsoft.Component.MSBuild", "Microsoft.VisualStudio.Component.CoreBuildTools", "Microsoft.VisualStudio.Workload.MSBuildTools", "Microsoft.Net.Component.4.TargetingPack" ], "extensions": [] }...
@CZEMacLeod For my last test I used the sample project provided by @julealgon which is set up to target 4.7.2: ``` ``` This is the same as my own test...
@CZEMacLeod That is not the issue. My web.config is definitely set up correctly (and is working as is in the legacy Web Site project with whatever language and framework versions...
@CZEMacLeod `10.0` versus `10` does not matter to the toolchain, they are aliased. In general, the language version warning does not happen consistently. I haven't been able to repro it...
Old share from old server mounted after deleting and recreating volume/deployment with the same name
Is there any workaround for this issue if I have encountered it? i.e. how do I force it to use the correct parameters?
Old share from old server mounted after deleting and recreating volume/deployment with the same name
/remove-lifecycle stale
Any updates? This issue is one of the top reasons that I always prefer bash over PowerShell, even in Azure Pipelines.
This issue is technically a regression. In version 0.86.0, dates before 1900 would not generate an exception when adding a `DataTable` as a worksheet, while in 0.96.0 an exception is...
The drive is set as a source folder for anime hashing and as a drop destination. All queues are empty on the server (everything idle), and the drive even spins...