- 17 12月, 2016 2 次提交
-
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
- 16 12月, 2016 10 次提交
-
-
由 John Hamby 提交于
Instrument the body of an expression-bodied lambda for dynamic analysis
-
由 John Hamby 提交于
-
由 John Hamby 提交于
-
由 Julien Couvreur 提交于
-
由 Julien Couvreur 提交于
-
由 Neal Gafter 提交于
Fixes #12940 Fixes #14110 Fixes #15640
-
由 AlekseyTs 提交于
Do not mark argument values as bad due to issues with names.
-
由 Jared Parsons 提交于
Check for assembly resolution errors in bootstrap build
-
由 Charles Stoner 提交于
VisualBasic function breakpoint binding
-
由 Heejae Chang 提交于
add PrimaryWorkspace concept in OOP
-
- 15 12月, 2016 17 次提交
-
-
由 Charles Stoner 提交于
Handle additional cases in MemberSemanticModel.GetQueryEnclosingBinder
-
-
由 Heejae Chang 提交于
-
由 John Hamby 提交于
-
由 Jared Parsons 提交于
-
由 Charles Stoner 提交于
-
由 Julien Couvreur 提交于
-
由 Jared Parsons 提交于
Our current setup for .Net Core requires us to do manual assembly redirection in our MSBuild Task. The setup has no good way to detect at compile time when our source code and NuGet references get out of date. This change allows us to at least detect at bootstrap time.
-
由 Andy Gocke 提交于
The problem is demonstrated by the following test case: ``` struct S { public int X, Y; } class C { public static void Main() { S s; s.X = 5; void Local() { s.Y = 10; System.Console.WriteLine(s); } Local(); // error CS0165: Use of unassigned local variable 's' } } ``` Definite assignment should allow structs to be assigned piecewise through a local function. The problem is that printing `s` is normally regarded as a use of `s`, not its constituent fields. This causes the analysis to effectively lose information about s.Y being assigned. The fix is, when recording captured reads of possibly unassigned structs in a local function, recursively record the possibly unassigned constituent fields, rather than the struct variable. Fixes #14097
-
由 Omar Tawfik 提交于
Add System.Xml.ReaderWriter.dll to compilers vsix
-
由 Jared Parsons 提交于
Fix race condition writing assembly attribute file
-
由 Omar Tawfik 提交于
-
由 CyrusNajmabadi 提交于
-
由 AlekseyTs 提交于
Fixes #15732.
-
由 Jared Parsons 提交于
MSBuild generates the TargetFrameworkAttribute file to the same path on disk for equivalent combinations of TargetFrameworkIdentifier and TargetProfile. This means if two projects in a solution have equivalent identifiers, their builds will race to write the same file to disk. This is safe by virtue that the content of the file is the same in both cases. Hence it doesn't really matter who wins the race, both projects see the same output. This is frustrating though because even though it's safe, MSBuild still isssue a warning when it happens. This breaks our desire to have warning free builds. To fix this we will instead generate the file to the Obj\ProjectName directory. This means every project gets their own indepnedent copy of the file, eliminating the race. closes #10116
-
由 Matt Warren 提交于
Add System.Runtime.InteropServices.RuntimeInformation to common nuget…
-
由 Dustin Campbell 提交于
Merge dev15-rc2 into master
-
- 14 12月, 2016 11 次提交
-
-
由 Dustin Campbell 提交于
-
由 Jonathon Marolf 提交于
Adds Prerequisites to vsixmanifest templates
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 AlekseyTs 提交于
Adjust scope of variables declared within a ‘for’ condition and ‘for’ incrementors.
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
Don't manually construct strings. It doesn't work for localization.
-
由 CyrusNajmabadi 提交于
-