- 29 3月, 2019 20 次提交
-
-
由 Heejae Chang 提交于
* fixed issue where we crash due to our pending async work run after VS shutdown this is another case where we have a pending async task that run after VS shutdown and it throws and our fail fast code catch that exception and crash VS. general fix will be some thing like us making our fail fast code to aware shutdown situation and ignore any exception if we are in the shutdown situation. but until we come up with proper design, this should handle one of high watson hits. * PR feedbacks
-
由 Sam Harwell 提交于
Fix flaky test AsynchronousOperationListenerTests.IgnoredCancel
-
由 Sam Harwell 提交于
Make struct types readonly in Microsoft.CodeAnalysis.Features
-
由 AlekseyTs 提交于
Merge Default Interface Methods feature into master
-
由 Jared Parsons 提交于
Verification for VS.ExternalAPIs.Roslyn package
-
由 Sam Harwell 提交于
Add ExternalAccess assembly for unit testing
-
由 Jared Parsons 提交于
-
由 Jason Malinowski 提交于
Workaround a CLR deadlock caused by unloading app domains with STA RCWs
-
由 Sam Harwell 提交于
-
由 Sam Harwell 提交于
-
由 Jared Parsons 提交于
-
由 AlekseyTs 提交于
-
由 Julien Couvreur 提交于
-
由 AlekseyTs 提交于
-
由 Heejae Chang 提交于
-
由 AlekseyTs 提交于
-
由 Joey Robichaud 提交于
Merge dev16.1-preview1 to master
-
由 Joey Robichaud 提交于
-
由 Jared Parsons 提交于
A recent refactoring caused a number of insertion failures as we weren't properly updating the contents of VS.ExternalAPIs.Roslyn.nupkg. This adds basic verification that the contents are correct based on our build output.
-
由 Joey Robichaud 提交于
* Added CSharp.Scripting to VS.ExternalApis pacakge * Add ExternalAccess to VS.ExternalApis package
-
- 28 3月, 2019 19 次提交
-
-
由 Shyam N 提交于
-
由 dotnet-automerge-bot 提交于
Merge dev16.1-preview1 to master
-
由 Joey Robichaud 提交于
-
由 Tomáš Matoušek 提交于
-
由 AlekseyTs 提交于
-
由 AlekseyTs 提交于
Merge 'dotnet/master' into DefaultInterfaceImplementation
-
由 Jared Parsons 提交于
Fix build correctness
-
由 Charles Stoner 提交于
-
由 Andrew Hall 提交于
Fix focus of items Fix accelerator key duplication Narrator reads the datagrid correctly
-
由 Joey Robichaud 提交于
-
由 Joey Robichaud 提交于
-
由 Jared Parsons 提交于
The project which deploys ILASM tools ends up bringing two runtime packages that have the same assets: - runtime.win-x64.microsoft.netcore.runtime.coreclr - runtime.win-x64.microsoft.netcore.app Specifically assets like SOS.NetCore.dll exists at different versions in these packages and end up getting copied twice to the output directory. This double write ends up breaking our build (as well as basic isolation). The short term fix here is to no longer treat this as a code project but instead a tools project. That eliminates the MS.NetCore.app package and the associated double writes Long term though the root issue needs to be addressed: making ilasm and ildasm easier to deploy. https://github.com/dotnet/coreclr/issues/15059
-
由 Sam Harwell 提交于
Remove duplicate PackageReference
-
由 Jason Malinowski 提交于
If you have an STA thread that created Runtime Callable Wrappers, it's possible to end up in a deadlock where the finalizer and app domain unload code are waiting for each other. The suggested workaround from the CLR team is to wait for finalizers before letting the domain shutdown but while the thread is still running. Fixes https://github.com/dotnet/roslyn/issues/34248
-
由 Sam Harwell 提交于
-
由 Sam Harwell 提交于
Fixes failure to correctly restore packages within Visual Studio 2019 RC.
-
由 Julien Couvreur 提交于
-
由 AlekseyTs 提交于
-
由 AlekseyTs 提交于
Microsoft.NETCore.App 3.0.0-preview4-27525-12, SDK version 3.0.100-preview4-010963
-
- 27 3月, 2019 1 次提交
-
-
由 Heejae Chang 提交于
* removed IEditorClassificationService that is marked obsolete since 2017 and bunch of other code that only existed for the IEditorClassificationService. according to vso, only F# still has dependency so I talked to them to move to new API (IClassificationService) - https://devdiv.visualstudio.com/DevDiv/_git/DotNet-Source-Build-Tarball?path=%2Fsrc%2Ffsharp%2Fvsintegration%2Fsrc%2FFSharp.Editor%2FClassification%2FColorizationService.fs&version=GBmaster and a bunch of clean up and move code that has no dependency to the editor to lower layers so that I can consume in razor scenario. * added shim project for FSharp that has internal visible to FSharp editor * merged https://github.com/dotnet/roslyn/pull/31941 * addressing PR feedback * moved some type (such as DocumentSpan, ClassifiedSpan and etc) back to where fsharp has IVT to. can't move those since partner team is using them and they don't have IVT to workspace layer for some reasons. also, have put the IEditorClassificationService back and add a proxy in FSharp External Access so that it can still work until they remove all IVT.
-