Signed-off-by: Louis DeJardin <email@example.com>
This is some preparation work for getting a build of Spark to function properly on mono out-of-box
The collection was restored before the view was reinserted, so it wasn't being added to the correct dictionary. The use of outerView._content prevents this from happenning regardless of the order of restoration.
A lot of times color doesn't appear when there are any compiler errors processing the spark files. This change attempts to have the color return in any case, but that won't help with intellisense not appearing in those cases.
Using a viewcomponent overriding SupportsSection, Spark doesn't check instance if there is a ViewComponentDetailsAttribute. Changed the behaviour for ViewComponentInfo to also check instance if attribute is found but doesn't mention section as supported.
It was only looking at the two known locations. The ability to put shared at several levels, like an area subfolder, wasn't working correctly.
Will throw a CompilerException if partials cause a circular dependency. Closes defect #2876 "Recursive partial views causes a stack overflow while compiling. Crashes Visual Studio." http://sparkviewengine.codeplex.com/WorkItem/View.aspx?WorkItemId=2876 Also fixes a problem where nested partials could each back-render parent content, which section the simpler "OuterPartial" property did not address correctly.
…variantCulture for the scope of the test
When RenderPartial was called from within a call to RenderPartial, there could be some output loss if they both attempt to write to a named content section that didn't exist before. This change binds the partial views to the content and once dictionaries directly so new entries are mutually available immediately.
This should allow users with customized color settings to continue using their existing scheme. It also means you can't have different color schemes for html and spark files, but that is much less of a problem.
This allows the Spark library in the AppDomain running in devenv process to disable error location manipulation. The error and warning reporting is much better that way.
The build number is no longer automatically applied from source control revision, so for release candidates it can be passed in as appropriate. The values used will follow the CI build numbers.
… of settings Signed-off-by: Louis DeJardin <firstname.lastname@example.org>
…and mvccontrib Signed-off-by: Louis DeJardin <email@example.com>
This is necessary for the colorization to be aware of the StatementMarker configuration property. Otherwise the color is always based on the '#' default.
WIX binaries are in the bin folder, so does not need to be installed on the building workstation. An empty packageloadkey.h is also created if the real one does not exist on disk. The resulting VSIP may be installed on machines which have the VS SDK installed, which is good for VSIP development and testing.