YAML for .NET, Visual Studio and Powershell

Closed Issue: Syntax highlighting conflicts with custom colors [7292]

yoav — Thu, 16 May 2013 09:12:34 GMT

The syntax highlighting should provide custom color classes as described in http://msdn.microsoft.com/en-us/library/bb165041.aspx (I'm assuming you use Managed Package Framework rather than Babel).

I use a custom color setup with light orange text on dark green to reduce eye-strain and allow a greater range of highlighting (since the text is light, different colors at the same brightness are much easier to distingush).

Source code checked in, #96133

Project Collection Service Accounts — Mon, 01 Oct 2012 21:40:31 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #96132

Project Collection Service Accounts — Mon, 01 Oct 2012 21:33:03 GMT

Checked in by server upgrade

Commented Issue: Yaml parser cannot handle comments [14972]

mas912 — Mon, 02 Apr 2012 18:09:08 GMT

'K1': V1 # comment
K2: 'V2' # not comment
'K3': 'V3' # again not comment and "Error 1 Expecting mapping key (YA112)", because line 2 is broken
Comments: ** Comment from web user: mas912 **

Yes.

Commented Issue: Yaml parser cannot handle comments [14972]

BurtHarris — Mon, 02 Apr 2012 17:39:25 GMT

'K1': V1 # comment
K2: 'V2' # not comment
'K3': 'V3' # again not comment and "Error 1 Expecting mapping key (YA112)", because line 2 is broken
Comments: ** Comment from web user: BurtHarris **

I'm assuming the text under description represents the YAML file that's generating the problem for you, right?

Created Issue: Yaml parser cannot handle comments [14972]

mas912 — Fri, 30 Mar 2012 12:17:23 GMT

'K1': V1 # comment
K2: 'V2' # not comment
'K3': 'V3' # again not comment and "Error 1 Expecting mapping key (YA112)", because line 2 is broken

New Post: Adopt for Visual Studio 2010

brisemec — Mon, 19 Sep 2011 10:56:04 GMT

Hello,

Is this project still alive? If so, when can you publish a VS2010 version?

Thanks

Source code checked in, #83498

ryaner — Sat, 10 Sep 2011 06:56:36 GMT

Fix for unit tests InEqualityNew, Y12_06_21, Y12_06_24, Y12_06_18, Y12_06_26, and Y12_08_21

Source code checked in, #83497

ryaner — Sat, 10 Sep 2011 02:50:10 GMT

Fix attempt for unit tests Y12_06_21, Y12_06_24, Y12_06_18, Y12_06_26, and Y12_08_21

Source code checked in, #83109

BurtHarris — Thu, 01 Sep 2011 17:31:18 GMT

Update tests so that error message displayed in Test Results window is more meaningful. Update the mechanism Presenter uses to match pending operations.

Source code checked in, #83077

BurtHarris — Thu, 01 Sep 2011 03:09:21 GMT

Trimming out obsolete code.

Source code checked in, #83062

BurtHarris — Wed, 31 Aug 2011 17:02:00 GMT

Splitting solutions for .Net2 and .Net4. This made obvious some strange references problems, which I've fixed up. They came back. I think the root cause of these is that the .Net2 and .Net4 projects (which were cloned) have the same project GUID, which confuses VS. I fixed that by giving all the .Net4 projects new GUIDs, and fixing up the references (hopefully for the last time.)

Source code checked in, #82992

BurtHarris — Tue, 30 Aug 2011 10:55:06 GMT

Big refactoring of serializer/deserializer code to make it more modular. Introduced the Tag struct which represents both a node's tag property (a URI) and its Kind. This introduced a few unit test errors.

Created Issue: Tag related test failures [14164]

BurtHarris — Tue, 30 Aug 2011 09:52:03 GMT

When I check in the Load update this evening, there will be 9 tests failing.   Most of them (if not all) are related to the new Tag structure and how YAML tag properties are getting parsed.   Have at them...
A bunch are based on example from the Yaml 1.2 spec.   Y12_06_21, Y12_06_24, Y12_06_18, Y12_06_26, and Y12_08_21. These failures probably have a common root cause.
InEquality - probably a bug in the test
NoLiteral - Haven't investaged

Workitem9840 and Workitem9817 have their own bugs.   You're welcome to try to tackle them too.

Commented Issue: Tags containing a # [9817]

BurtHarris — Tue, 30 Aug 2011 04:22:15 GMT

Getting YA308 on tags containing a fragment (embedded #)
Comments: Perhaps it mutated, its now generating a YA308 not a YA309. I'm going to complete the refactoring of Loader before assigning.

Commented Issue: Tags containing a # [9817]

BurtHarris — Tue, 30 Aug 2011 04:02:20 GMT

Getting YA309 on tags containing a fragment (embedded #)
Comments: Adding a unit test for this in YamlBasicsTest.cs.

Closed Issue: CA1502 : AvoidExcessiveComplexity in Emitter.cs consturctor [13107]

BurtHarris — Tue, 30 Aug 2011 03:54:17 GMT

Comments: Emitter class no lonter exists.

Closed Issue: Unit tests fail in Debug Build [14089]

BurtHarris — Tue, 30 Aug 2011 03:48:44 GMT

The CoreUnitTest module has 56 tests that fail when run under the Debug build.

This appears to have something to do with the code contracts "rewriter" not adding required information to the assembly before running the test. Error messages look something like this, with reference to $evaluatingInvariant$ being the tipoff it has something to do with the code contracts rewriter.

Test method YaTools.Yaml.UnitTests.Y12ExamplesAuto.Y12_05_12 threw exception:
System.MissingFieldException: Field not found: 'YaTools.Yaml.YamlParser.$evaluatingInvariant$'.

Note: No longer happens. I don't know what I did to fix this. There are two tests currently failing, but they are related to issues I recently introduced around serialization (class Dump) and tagging of dump output.
Comments: Confirmed this no longer happens, under either debug or release builds.

Commented Issue: Unit tests fail in Debug Build [14089]

BurtHarris — Tue, 30 Aug 2011 03:43:30 GMT

Ryan says this is not reproducing.

Source code checked in, #82840

BurtHarris — Sat, 27 Aug 2011 21:12:33 GMT

Code reformatted w/ Resharper