silk Issue Tracker Rss Feed

Commented Issue: A project with an output type of class library cannot be started directly message [8127]

DCherubini — Wed, 06 Mar 2013 20:35:07 GMT

Even if I have set MileageStat.Web as start up project, I still get the dialog message "A project with an output type of class library cannot be started directly"

Could you please help ?
Comments: Hi, As far as I know, this kind of problems could appear if a file corresponding to the __Visual Studio__ solution is corrupted. As a starting point, I believe you could try deleting the __.gpState__ and __.suo__ files in the solution directory (the later ones are hidden) as well as the __bin__ and __obj__ folders and then select the __MileageStat.Web__ project as the __StartUp Project__ again. Also, remember to select the corresponding page inside the project as the __Start Page__ . As a side note, it seems this problem is more related to __Visual Studio__ than __Silk__ , so I believe you might find better support in the __Visual Studio__ forums: - [Visual Studio Forums in Social MSDN](http://social.msdn.microsoft.com/Forums/en/category/visualstudio) Regards, Damian Cherubini http://blogs.southworks.net/dcherubini

Created Issue: A project with an output type of class library cannot be started directly message [8127]

pnagori02 — Mon, 25 Feb 2013 17:50:01 GMT

Even if I have set MileageStat.Web as start up project, I still get the dialog message "A project with an output type of class library cannot be started directly"

Could you please help ?

Commented Issue: The lack of Cassini support should be better handled or documented. [8113]

ismarDude — Thu, 24 Jan 2013 06:41:52 GMT

From the following thread in the discussions:
http://silk.codeplex.com/discussions/269886

At the very least this note in code should also be placed as part of the installation notes and also where the call hangs.

// Note: On a development server (Cassini) you may get a serializationexception
// with custom identities.
//

For as much effort as went into this project, I don't understand why a workaround wasn't implemented.

System.InvalidOperationException was unhandled by user code
Message=There is an error in XML document (0, 0).
Source=System.Xml
StackTrace:
at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
at System.Xml.Serialization.XmlSerializer.Deserialize(TextReader textReader)
at MileageStats.Domain.Models.UserInfo.FromString(String userContextData) in C:\Users\SGM7\Documents\Silk\MileageStats\MileageStats.Domain\Models\UserInfo.cs:line 43
at MileageStats.Web.Models.MileageStatsIdentity..ctor(FormsAuthenticationTicket ticket) in C:\Users\SGM7\Documents\Silk\MileageStats\MileageStats.Web\Models\MileageStatsIdentity.cs:line 46
at MileageStats.Web.MvcApplication.PostAuthenticateRequestHandler(Object sender, EventArgs e) in C:\Users\SGM7\Documents\Silk\MileageStats\MileageStats.Web\Global.asax.cs:line 156
at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
InnerException: System.Xml.XmlException
Message=Root element is missing.
Source=System.Xml
LineNumber=0
LinePosition=0
SourceUri=""
StackTrace:
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.XmlTextReader.Read()
at System.Xml.XmlReader.MoveToContent()
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderUserInfo.Read3_UserInfo()
InnerException:
Comments: in my case adding a generated machine Key to the config file helped (using http://aspnetresources.com/tools/machineKey tool) something like <machineKey validationKey="3B4630393E490E7D5F0CEDAFC832E6C75FD0F6A916C9D5C2E36244737795EC594F42DA5CAA6C38CBEBDB20E89FED067BC3D6812AA083B98A14286466451777C1" decryptionKey="A219CA4EF9495433CB43560685760EEA5879EC8C4161638DA923065801348B8B" validation="SHA1" decryption="AES" />

Commented Issue: The lack of Cassini support should be better handled or documented. [8113]

ismarDude — Thu, 24 Jan 2013 06:18:14 GMT

Commented Issue: Multiple errors when running initial build [8126]

SkildLobster — Sat, 15 Dec 2012 15:56:11 GMT

I tried the OpenAuth fix in web.config and that did not resolve that issue either, but here is a list of all the build errors I'm getting below. Also the NuGet installation working without issue. Thanks in advance for any help.

Error 1 The name 'DatabaseGeneratedOption' does not exist in the current context C:\ProjectsJames\SilkDev\MileageStats\MileageStats.Data.SqlCe\MileageStatsDbContext.cs 57 45 MileageStats.Data.SqlCe
Error 2 The name 'DatabaseGeneratedOption' does not exist in the current context C:\ProjectsJames\SilkDev\MileageStats\MileageStats.Data.SqlCe\MileageStatsDbContext.cs 67 17 MileageStats.Data.SqlCe
Error 3 The name 'DatabaseGeneratedOption' does not exist in the current context C:\ProjectsJames\SilkDev\MileageStats\MileageStats.Data.SqlCe\MileageStatsDbContext.cs 76 45 MileageStats.Data.SqlCe
Error 4 The name 'DatabaseGeneratedOption' does not exist in the current context C:\ProjectsJames\SilkDev\MileageStats\MileageStats.Data.SqlCe\MileageStatsDbContext.cs 88 45 MileageStats.Data.SqlCe
Error 5 The name 'DatabaseGeneratedOption' does not exist in the current context C:\ProjectsJames\SilkDev\MileageStats\MileageStats.Data.SqlCe\MileageStatsDbContext.cs 104 45 MileageStats.Data.SqlCe
Error 6 The name 'DatabaseGeneratedOption' does not exist in the current context C:\ProjectsJames\SilkDev\MileageStats\MileageStats.Data.SqlCe\MileageStatsDbContext.cs 114 45 MileageStats.Data.SqlCe
Error 7 The name 'DatabaseGeneratedOption' does not exist in the current context C:\ProjectsJames\SilkDev\MileageStats\MileageStats.Data.SqlCe\MileageStatsDbContext.cs 129 45 MileageStats.Data.SqlCe
Error 8 Metadata file 'C:\ProjectsJames\SilkDev\MileageStats\MileageStats.Data.SqlCe\bin\Debug\MileageStats.Data.SqlCe.dll' could not be found MileageStats.Data.SqlCe.Tests
Error 9 Metadata file 'C:\ProjectsJames\SilkDev\MileageStats\MileageStats.Data.SqlCe\bin\Debug\MileageStats.Data.SqlCe.dll' could not be found MileageStats.Web
Error 10 Metadata file 'C:\ProjectsJames\SilkDev\MileageStats\MileageStats.Web\bin\MileageStats.Web.dll' could not be found MileageStats.Web.Tests
Error 11 Metadata file 'C:\ProjectsJames\SilkDev\MileageStats\MileageStats.Web\bin\MileageStats.Web.dll' could not be found MileageStats.Services.Tests
Error 12 Metadata file 'C:\ProjectsJames\SilkDev\MileageStats\MileageStats.Data.SqlCe\bin\Debug\MileageStats.Data.SqlCe.dll' could not be found MileageStats.Services.Tests
Warning 13 Could not resolve this reference. Could not locate the assembly "DotNetOpenAuth". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. MileageStats.Web
Warning 14 Could not resolve this reference. Could not locate the assembly "DotNetOpenAuth". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. MileageStats.Web.Tests
Warning 15 The referenced component 'DotNetOpenAuth' could not be found.
Warning 16 The referenced component 'DotNetOpenAuth' could not be found.

Comments: I tried to run this under Visual Studio 2010 Ultimate. I will try the measures you mentioned above and reply back. Thanks!

Commented Issue: Multiple errors when running initial build [8126]

aadami — Fri, 07 Dec 2012 13:40:12 GMT

I tried the OpenAuth fix in web.config and that did not resolve that issue either, but here is a list of all the build errors I'm getting below. Also the NuGet installation working without issue. Thanks in advance for any help.

Error 1 The name 'DatabaseGeneratedOption' does not exist in the current context C:\ProjectsJames\SilkDev\MileageStats\MileageStats.Data.SqlCe\MileageStatsDbContext.cs 57 45 MileageStats.Data.SqlCe
Error 2 The name 'DatabaseGeneratedOption' does not exist in the current context C:\ProjectsJames\SilkDev\MileageStats\MileageStats.Data.SqlCe\MileageStatsDbContext.cs 67 17 MileageStats.Data.SqlCe
Error 3 The name 'DatabaseGeneratedOption' does not exist in the current context C:\ProjectsJames\SilkDev\MileageStats\MileageStats.Data.SqlCe\MileageStatsDbContext.cs 76 45 MileageStats.Data.SqlCe
Error 4 The name 'DatabaseGeneratedOption' does not exist in the current context C:\ProjectsJames\SilkDev\MileageStats\MileageStats.Data.SqlCe\MileageStatsDbContext.cs 88 45 MileageStats.Data.SqlCe
Error 5 The name 'DatabaseGeneratedOption' does not exist in the current context C:\ProjectsJames\SilkDev\MileageStats\MileageStats.Data.SqlCe\MileageStatsDbContext.cs 104 45 MileageStats.Data.SqlCe
Error 6 The name 'DatabaseGeneratedOption' does not exist in the current context C:\ProjectsJames\SilkDev\MileageStats\MileageStats.Data.SqlCe\MileageStatsDbContext.cs 114 45 MileageStats.Data.SqlCe
Error 7 The name 'DatabaseGeneratedOption' does not exist in the current context C:\ProjectsJames\SilkDev\MileageStats\MileageStats.Data.SqlCe\MileageStatsDbContext.cs 129 45 MileageStats.Data.SqlCe
Error 8 Metadata file 'C:\ProjectsJames\SilkDev\MileageStats\MileageStats.Data.SqlCe\bin\Debug\MileageStats.Data.SqlCe.dll' could not be found MileageStats.Data.SqlCe.Tests
Error 9 Metadata file 'C:\ProjectsJames\SilkDev\MileageStats\MileageStats.Data.SqlCe\bin\Debug\MileageStats.Data.SqlCe.dll' could not be found MileageStats.Web
Error 10 Metadata file 'C:\ProjectsJames\SilkDev\MileageStats\MileageStats.Web\bin\MileageStats.Web.dll' could not be found MileageStats.Web.Tests
Error 11 Metadata file 'C:\ProjectsJames\SilkDev\MileageStats\MileageStats.Web\bin\MileageStats.Web.dll' could not be found MileageStats.Services.Tests
Error 12 Metadata file 'C:\ProjectsJames\SilkDev\MileageStats\MileageStats.Data.SqlCe\bin\Debug\MileageStats.Data.SqlCe.dll' could not be found MileageStats.Services.Tests
Warning 13 Could not resolve this reference. Could not locate the assembly "DotNetOpenAuth". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. MileageStats.Web
Warning 14 Could not resolve this reference. Could not locate the assembly "DotNetOpenAuth". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. MileageStats.Web.Tests
Warning 15 The referenced component 'DotNetOpenAuth' could not be found.
Warning 16 The referenced component 'DotNetOpenAuth' could not be found.

Comments: So far I could reproduce the aforementioned errors when building MileageStats in Visual Studio 2012. In order to avoid them I have to make the following changes: -Removed the reference to DotNetOpenAuth assembly (as it's from an older version than the one installed by Nuget) from the MileageStats.Web and MileageStats.Web.Tests projects -Added the following statement to the MileageStatsDbContext.cs file in the MileageStats.Data.SqlCe project to avoid the The name 'DatabaseGeneratedOption' does not exist in the current context error : using System.ComponentModel.DataAnnotations.Schema; As it seems that there have been changes in this namespace if you installed Entity Framework version 5.x. Also, as you mentioned you will also have to remove the surplus section in the Web.Config in MileageStats.Web:  After doing these changes I could build and run the sample without problems. Regards, Agustin Adami http://blogs.southworks.net/aadami

Commented Issue: Multiple errors when running initial build [8126]

aadami — Thu, 06 Dec 2012 12:30:40 GMT

I tried the OpenAuth fix in web.config and that did not resolve that issue either, but here is a list of all the build errors I'm getting below. Also the NuGet installation working without issue. Thanks in advance for any help.

Error 1 The name 'DatabaseGeneratedOption' does not exist in the current context C:\ProjectsJames\SilkDev\MileageStats\MileageStats.Data.SqlCe\MileageStatsDbContext.cs 57 45 MileageStats.Data.SqlCe
Error 2 The name 'DatabaseGeneratedOption' does not exist in the current context C:\ProjectsJames\SilkDev\MileageStats\MileageStats.Data.SqlCe\MileageStatsDbContext.cs 67 17 MileageStats.Data.SqlCe
Error 3 The name 'DatabaseGeneratedOption' does not exist in the current context C:\ProjectsJames\SilkDev\MileageStats\MileageStats.Data.SqlCe\MileageStatsDbContext.cs 76 45 MileageStats.Data.SqlCe
Error 4 The name 'DatabaseGeneratedOption' does not exist in the current context C:\ProjectsJames\SilkDev\MileageStats\MileageStats.Data.SqlCe\MileageStatsDbContext.cs 88 45 MileageStats.Data.SqlCe
Error 5 The name 'DatabaseGeneratedOption' does not exist in the current context C:\ProjectsJames\SilkDev\MileageStats\MileageStats.Data.SqlCe\MileageStatsDbContext.cs 104 45 MileageStats.Data.SqlCe
Error 6 The name 'DatabaseGeneratedOption' does not exist in the current context C:\ProjectsJames\SilkDev\MileageStats\MileageStats.Data.SqlCe\MileageStatsDbContext.cs 114 45 MileageStats.Data.SqlCe
Error 7 The name 'DatabaseGeneratedOption' does not exist in the current context C:\ProjectsJames\SilkDev\MileageStats\MileageStats.Data.SqlCe\MileageStatsDbContext.cs 129 45 MileageStats.Data.SqlCe
Error 8 Metadata file 'C:\ProjectsJames\SilkDev\MileageStats\MileageStats.Data.SqlCe\bin\Debug\MileageStats.Data.SqlCe.dll' could not be found MileageStats.Data.SqlCe.Tests
Error 9 Metadata file 'C:\ProjectsJames\SilkDev\MileageStats\MileageStats.Data.SqlCe\bin\Debug\MileageStats.Data.SqlCe.dll' could not be found MileageStats.Web
Error 10 Metadata file 'C:\ProjectsJames\SilkDev\MileageStats\MileageStats.Web\bin\MileageStats.Web.dll' could not be found MileageStats.Web.Tests
Error 11 Metadata file 'C:\ProjectsJames\SilkDev\MileageStats\MileageStats.Web\bin\MileageStats.Web.dll' could not be found MileageStats.Services.Tests
Error 12 Metadata file 'C:\ProjectsJames\SilkDev\MileageStats\MileageStats.Data.SqlCe\bin\Debug\MileageStats.Data.SqlCe.dll' could not be found MileageStats.Services.Tests
Warning 13 Could not resolve this reference. Could not locate the assembly "DotNetOpenAuth". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. MileageStats.Web
Warning 14 Could not resolve this reference. Could not locate the assembly "DotNetOpenAuth". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. MileageStats.Web.Tests
Warning 15 The referenced component 'DotNetOpenAuth' could not be found.
Warning 16 The referenced component 'DotNetOpenAuth' could not be found.

Comments: Hi, It would be helpful to know which version of Visual Studio are you using to run the sample. As this could help in order to reproduce the error you are mentioning. Regards, Agustin Adami http://blogs.southworks.net/aadami

Created Issue: Multiple errors when running initial build [8126]

SkildLobster — Fri, 30 Nov 2012 20:33:05 GMT

Commented Issue: The lack of Cassini support should be better handled or documented. [8113]

etlds — Wed, 31 Oct 2012 15:40:01 GMT

From the following thread in the discussions:
http://silk.codeplex.com/discussions/269886

At the very least this note in code should also be placed as part of the installation notes and also where the call hangs.

// Note: On a development server (Cassini) you may get a serializationexception
// with custom identities.
//

For as much effort as went into this project, I don't understand why a workaround wasn't implemented.

System.InvalidOperationException was unhandled by user code
Message=There is an error in XML document (0, 0).
Source=System.Xml
StackTrace:
at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
at System.Xml.Serialization.XmlSerializer.Deserialize(TextReader textReader)
at MileageStats.Domain.Models.UserInfo.FromString(String userContextData) in C:\Users\SGM7\Documents\Silk\MileageStats\MileageStats.Domain\Models\UserInfo.cs:line 43
at MileageStats.Web.Models.MileageStatsIdentity..ctor(FormsAuthenticationTicket ticket) in C:\Users\SGM7\Documents\Silk\MileageStats\MileageStats.Web\Models\MileageStatsIdentity.cs:line 46
at MileageStats.Web.MvcApplication.PostAuthenticateRequestHandler(Object sender, EventArgs e) in C:\Users\SGM7\Documents\Silk\MileageStats\MileageStats.Web\Global.asax.cs:line 156
at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
InnerException: System.Xml.XmlException
Message=Root element is missing.
Source=System.Xml
LineNumber=0
LinePosition=0
SourceUri=""
StackTrace:
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.XmlTextReader.Read()
at System.Xml.XmlReader.MoveToContent()
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderUserInfo.Read3_UserInfo()
InnerException:
Comments: When I run at release mode. This error ran away. I don't know why...

Created Issue: Section or group name 'dotNetOpenAuth' is already defined [8125]

aadami — Wed, 13 Jun 2012 12:35:10 GMT

It seems that there is an extra section definition in the web.config file. After installing the required Nuget Packages and completing all required steps. When running the application the following error is thrown:

Section or group name 'dotNetOpenAuth' is already defined. This can not be defined multiple times.

In my case I could avoid this error by removing the following section definition in the web.config file (which was present before the Nuget Package installation):

<section name="dotNetOpenAuth" type="DotNetOpenAuth.Configuration.DotNetOpenAuthSection" requirePermission="false" allowLocation="true" />

Commented Issue: JavaScript Unit Tests Failing [8117]

dosname50 — Sat, 02 Jun 2012 12:40:02 GMT

I just downloaded the source materials and ran through the setup procedures, including the JavaScript unit testing. When I ran the unit tests, the unit tests failed to complete. I tracked the cause down to the fact that the distribution
appears to be using the QUnit stop and start methods in an obsolete way.

Specifically, the stop method is called with a very large number that appears to be a timeout value. The documentation on the QUnit site says:

The optional argument allows you to compress multiple stop() calls into one, e.g. stop(2) has the same effect as stop(); stop().

Note: This used to be the timeout argument, which was never recommended for use in non-debugging code. If you need a global timeout, set QUnit.config.testTimeout instead.

I made some adjustments to the tests to bring them into compliance with the currently available copy of QUnit. Now all of the JavaScript tests pass. These changes ought to be included in a future distribution or a comment
should be made in the setup procedures to indicate which version of the QUnit package should be used.

Jon Stonecash
Comments: Hi, you don't mention about dates in charts... The home controller JsonGetFleetStatisticSeries action return months without zero based month index. In client side javascript mstats.charts.js: _setupDateRange sets datesInDateRange with zero based month index so _filterSeriesByDateRange does not filters data series well because _isDateInRange.

Commented Issue: Run issue on Visual Studio 11 Express Web Edition [8124]

GerardVeneman — Tue, 22 May 2012 07:44:59 GMT

Edited Issue: Run issue on Visual Studio 11 Express Web Edition [8124]

GerardVeneman — Tue, 22 May 2012 07:44:59 GMT

Commented Issue: Run issue on Visual Studio 11 Express Web Edition [8124]

aadami — Mon, 21 May 2012 18:14:42 GMT

After installing the external js scripts and running the NuGet installer script the project won't build on VS 11 Express Web Edition because of the Code Analysis feature.

Fortunately this can be disabled in all four sub-projects using the sub-project property page 'Code Analysis' tab. This, or any better solution off course, should be added to the manual.
Comments: Hi, We have been able to reproduce this behavior. When building the solution (after following all installation steps) in Visual Studio 2011 Express Web Edition beta, many build errors are thrown. On the other hand when we installed MilageStats in Visual Studio 2011 Beta Ultimate, there were no build errors. It seems that the Express version runs only the basic analysis. In this version, you don't have access to the configuration tools on the Analyze menu, therefore I believe the custom rule sets that come by default with the application are not being loaded, and these build errors appear. In this case we verify that disabling the Enable Code Analysis on Build feature from the projects property page 'Code Analysis' tab as mentioned avoids the errors. Additionally, when running the application we encountered the following error: ...Section or group name 'dotNetOpenAuth' is already defined. This can not be defined multiple times. It seems that there may be an extra section definition in the web.config file after installing the NuGet packages. As we could avoid this error by removing the following section definition from the web.config file: <section name="dotNetOpenAuth" type="DotNetOpenAuth.Configuration.DotNetOpenAuthSection" requirePermission="false" allowLocation="true" /> Thanks, Agustin Adami http://blogs.southworks.net/aadami

Edited Issue: Run issue on Visual Studio 11 Express Web Edition [8124]

GerardVeneman — Tue, 08 May 2012 19:55:20 GMT

Edited Issue: Run issue on Visual Studio 11 Express Web Edition [8124]

GerardVeneman — Tue, 08 May 2012 18:55:30 GMT

After installing the external js scripts and running the NuGet installer script the project still won't build on VS 11 Express Web Edition because of the Code Analysis feature. Fortunately this can be disabled in all four sub-projects using the sub-project property page 'Code Analysis' tab. This, or any better solution off course, should be added to the manual.

My real issue is this; The project will build but the following inner exception is thrown in FromString in UserInfo on VS 11 Express WE, in both the VS Dev Server as IIS Express. Sometimes it runs on Chrome but crashes on IE, sometimes it's the other way 'round...

{System.Xml.XmlException: Root element is missing.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.XmlTextReader.Read()
at System.Xml.XmlReader.MoveToContent()
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderUserInfo.Read3_UserInfo()}

Edited Issue: Run issue on Visual Studio 11 Express Web Edition [8124]

GerardVeneman — Tue, 08 May 2012 18:13:42 GMT

After installing the external js scripts and running the NuGet installer script the project still won't build on VS 11 Express Web Edition because of the Code Analysis feature. Fortunately this can be disabled in all four sub-projects using the sub-project property page 'Code Analysis' tab. This, or any better solution off course, should be added to the manual.

My real issue is this; The project will build but the following inner exception is thrown in FromString in UserInfo on VS 11 Express WE, in both the VS Dev Server as IIS Express when running through Google Chrome 18. In IE it appears to work correctly.

{System.Xml.XmlException: Root element is missing.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.XmlTextReader.Read()
at System.Xml.XmlReader.MoveToContent()
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderUserInfo.Read3_UserInfo()}

Created Issue: Run issue on Visual Studio 11 Express Web Edition [8124]

GerardVeneman — Tue, 08 May 2012 18:08:22 GMT

After installing the external js scripts and running the NuGet installer script the project still won't build on VS 11 Express Web Edition because of the Code Analysis feature. Fortunately this can be disabled in all four sub-projects using the sub-project property page 'Code Analysis' tab. This, or any better solution off course, should be added to the manual.

My real issue is this; The project will build but the following inner exception is thrown in FromString in UserInfo on VS 11 Express WE, in both the VS Dev Server as IIS Express.

{System.Xml.XmlException: Root element is missing.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.XmlTextReader.Read()
at System.Xml.XmlReader.MoveToContent()
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderUserInfo.Read3_UserInfo()}

Commented Issue: Unit of Work: handling multiple repository implementations [8116]

aadami — Fri, 04 May 2012 17:45:36 GMT

The user shijuvar (http://www.codeplex.com/site/users/view/shijuvar) has mentioned in this thread in the discussions (http://silk.codeplex.com/discussions/271579) that it would be advantageous to
implement the Unit of Work pattern for handling multiple repository implementations.

Regards,
Agustin Adami
http://blogs.southworks.net/aadami
Comments: Hi, For those interested, I also found the following tutorial from the Getting Started with EF using MVC series interesting, regarding how to implement the Repository and Unit of Work Patterns: Implementing the Repository and Unit of Work Patterns in an ASP.NET MVC Application http://www.asp.net/mvc/tutorials/getting-started-with-ef-using-mvc/implementing-the-repository-and-unit-of-work-patterns-in-an-asp-net-mvc-application Regards, Agustin Adami http://blogs.southworks.net/aadami

Closed Issue: Quickstart functionality [8122]

DCherubini — Thu, 26 Apr 2012 19:17:48 GMT

While I was trying it at default.htm the first thing I did was to change:

---- start file: jquery.qs.tagger.js -----
....
hideAfter = 1000; //ms
...
---- end file: jquery.qs.tagger.js -----

to
---- start file: jquery.qs.tagger.js -----
...
hideAfter = 5000; // ms
...
---- end file: jquery.qs.tagger.js -----

but it wasn't hidding after five second!!!

I Know it's an example but I wanted to share my experience.

Congratulations because this project was what I were looking for!
I'm studing it and I'm learning a lot!
Thanks you!
Comments: Hi, We are closing this work item as, as mentioned by Agustin, the issue described here could not be reproduced and it is probably not an issue in Silk. Regards, Damian Cherubini http://blogs.southworks.net/dcherubini