- 28 10月, 2016 1 次提交
-
-
由 Jared Parsons 提交于
-
- 26 10月, 2016 1 次提交
-
-
由 Jared Parsons 提交于
-
- 24 10月, 2016 5 次提交
-
-
由 Jared Parsons 提交于
This should either be defined globally or not at all. Repeating all the logic on a local level is just wasted time.
-
由 Jared Parsons 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
- 22 10月, 2016 3 次提交
-
-
由 Jared Parsons 提交于
TLDR: artifacts are going to move around in Binaries\Debug and the directory is going to get a lot bigger. At a high level build projects can be classified into three categories based on how they write output: - incorrect: a given output path is written to more than once with different contents - less correct: a given output path is written to more than once but always with the same content - correct: a given output path is written to exactly once Today the roslyn build is decidedly “incorrect” as pretty much every file is written directly into Binaries\Debug. This means it ends up writing pretty much every Visual Studio SDK DLL twice: once for Dev14 and once for Dev15. For example at various points in the build Binaries\Debug\Microsoft.VisualStudio.Text.Data.dll may refer to Dev14 and at others it’s Dev15. If this seems like a scary proposition for a build that’s because it is indeed scary and it has real consequences. By now pretty much everyone on the team has hit the build race condition that is dragging down our PRs. The general fix here is to move build outputs into separate directories. Instead of building to $(Configuration) projects now build into say $(Configuration)\Exes\$(MSBuildProjectFileName). This will have a substantial increase in the size of Binaries. We will be looking into ways to reduce that. In the short term though build stability far outweighs the size increase. This change takes us most of the way to "correct". There are several places I had to compromise in order to get this initial change in: - UnitTests still build to a common output folder (one for Dev14, another for Dev15). Pulling unit tests apart is going to take a bit of work. - Every project has a <RoslynProjectType> entry. This will go away in the future for most projects. It's temporarily needed so I can fix roslyn-internal in parallel without taking down the build. - VSL.Imports.targets is messy. Unavoidable for now due to the above. It will get cleaner as I iterate on this. None of these are relevant to the underlying race condition. Hence it's okay to push them off.
-
由 CyrusNajmabadi 提交于
-
由 David Poeschl 提交于
This allows the VSI option resetter to reset the option (so that stale default values aren't used).
-
- 21 10月, 2016 5 次提交
-
-
由 Heejae Chang 提交于
fixed 2 issue where IDE analyzer throws null exception and host analyzer exception message not going away from error list issue.
-
由 Ravi Chande 提交于
-
由 Ravi Chande 提交于
My forms completion
-
由 Fredric Silberberg 提交于
-
由 David Poeschl 提交于
This reverts commit 9f30b914.
-
- 20 10月, 2016 4 次提交
-
-
由 David Poeschl 提交于
This reverts commit 12ce69e2. Reverting this because it is causing VSI test failures, especially around Razor.
-
由 Heejae Chang 提交于
fixed 2 issue where IDE analyzer throws null exception and host analyzer exception message not going away from error list issue.
-
由 Heejae Chang 提交于
workspace will cache everything in memory if this service doesn't exist in workspace. now this being exist, workspace will start to put things such as text, tree, compilation either kick out from memory or save it to temporary storage. this should reduce memory foot print once things become idle, but this doesn't help memory footprint while feature is running. with this service, once OOP become idle, memory foot print goes down to about 700MB to 1 GB. but still while code lens run, memory goes up to 3GB.
-
由 David Poeschl 提交于
This change also introduces Specification and Style management (deleting and editing). Also, fixes #14358
-
- 19 10月, 2016 9 次提交
-
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 Heejae Chang 提交于
avoid loading dlls not needed
-
由 Heejae Chang 提交于
-
由 David Poeschl 提交于
Fixes #14159 The well-known ValueTuple types are very special in that you can ask for the SymbolInfo on the ValueTuple token and not get back the ValueTuple type. This means that the token we invoke rename on has no locations, which Rename Tracking mistakenly interpreted as being okay to rename. This has been fixed, and also the RenameUtilities.GetTokenRenameInfo method has been updated to return NoSymbolsTokenInfo when it finds an ITypeSymbol with IsTupleType.
-
由 Heejae Chang 提交于
-
由 VSadov 提交于
We were missing a null check fo the container. In broken code it can be null. Fixes: #14546
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
- 18 10月, 2016 8 次提交
-
-
由 Heejae Chang 提交于
-
由 Ravi Chande 提交于
Suggest types (and intrinsic type keywords) after "(" when declaring a tuple type as the type of a member. Fixes #14127
-
由 CyrusNajmabadi 提交于
-
由 Heejae Chang 提交于
-
由 Ravi Chande 提交于
-
由 Ravi Chande 提交于
-
由 Ravi Chande 提交于
-
由 Ravi Chande 提交于
-
- 16 10月, 2016 4 次提交
-
-
由 Heejae Chang 提交于
Fixed null exception for solution which has both C#/VB and typescript/javascript
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-