<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="/rss.xsl"?><rss version="2.0"><channel><title>NBusiness Work Item Rss Feed</title><link>http://www.codeplex.com/WorkItem/List.aspx?ProjectName=NBusiness</link><description>NBusiness Work Item Rss Description</description><item><title>CREATED FEATURE: Allow Configuration of Template and Validation Rule  Frameworks</title><link>http://www.codeplex.com/NBusiness/WorkItem/View.aspx?WorkItemId=15656</link><description>A user should be able to have a way to specify which validation rule and template frameworks to use at compile time. In order to validate those declarations in their es files they need to have a way to specify the base types and&amp;#47;or engines associated with the rules they wish to use.&lt;br /&gt;</description><author>justinc</author><pubDate>Sat, 15 Mar 2008 15:05:37 GMT</pubDate><guid isPermaLink="false">CREATED FEATURE: Allow Configuration of Template and Validation Rule  Frameworks 20080315030537P</guid></item><item><title>COMMENTED FEATURE: Template: JSON data format</title><link>http://www.codeplex.com/NBusiness/WorkItem/View.aspx?WorkItemId=15361</link><description>Output code handlers that can be queried against by a web application using Javascript JSON data format.  This would entail returning the data in JSON fashion, just like getting the object&amp;#39;s xml using the EntityInfoBase etc.   Basically the handller should output JSON like&amp;#58;&lt;br /&gt;&lt;br /&gt;JSONStream ouput &amp;#61; &amp;#60;Handlers&amp;#62;.Blog.Fetch&amp;#40;0&amp;#41; &amp;#59;&lt;br /&gt;&lt;br /&gt;OR&lt;br /&gt;&lt;br /&gt;JSONStream output &amp;#61; Blog.Fetch&amp;#40;0&amp;#41;.toJSON&amp;#40;&amp;#41;&amp;#59;  &amp;#40;then leave the implementation up to the developer&amp;#41;&lt;br /&gt;Comments: ** Comment from web user: justinc ** &lt;p&gt;I&amp;#39;m not sure I understand this one fully, isn&amp;#39;t this all taken care of automatically by webservices&amp;#63; I guess I am not familiar with the JSONStream object can you explain that a bit more&amp;#63;&lt;/p&gt;</description><author>justinc</author><pubDate>Thu, 28 Feb 2008 14:42:21 GMT</pubDate><guid isPermaLink="false">COMMENTED FEATURE: Template: JSON data format 20080228024221P</guid></item><item><title>COMMENTED FEATURE: Template: MVC Controllers Interaction With Models</title><link>http://www.codeplex.com/NBusiness/WorkItem/View.aspx?WorkItemId=15363</link><description>The idea here is to output code based on some format that said how you could interact with Models.  Simply put this is a way to obtain free code that implement the MVC Controller architecture.  Would be simple fetching and standard CRUD &amp;#34;Actions&amp;#34;.&lt;br /&gt;Comments: ** Comment from web user: justinc ** &lt;p&gt;It should be called MvcControllerTemplate, it could use the &amp;#34;Action&amp;#34; declarations on models or entities. This shouldn&amp;#39;t be too hard, the only tricks I can forsee will be building actions for things like viewing lists with paging without making too many ugly actions. They should be partial too so they can be extended. Actually they would need to have a certain namespace too to follow the convention... that could complicate things.&lt;/p&gt;</description><author>justinc</author><pubDate>Thu, 28 Feb 2008 14:40:26 GMT</pubDate><guid isPermaLink="false">COMMENTED FEATURE: Template: MVC Controllers Interaction With Models 20080228024026P</guid></item><item><title>CREATED FEATURE: Template: MVC Controllers Interaction With Models</title><link>http://www.codeplex.com/NBusiness/WorkItem/View.aspx?WorkItemId=15363</link><description>The idea here is to output code based on some format that said how you could interact with Models.  Simply put this is a way to obtain free code that implement the MVC Controller architecture.  Would be simple fetching and standard CRUD &amp;#34;Actions&amp;#34;.&lt;br /&gt;</description><author>kleneau</author><pubDate>Wed, 27 Feb 2008 17:34:45 GMT</pubDate><guid isPermaLink="false">CREATED FEATURE: Template: MVC Controllers Interaction With Models 20080227053445P</guid></item><item><title>CREATED ISSUE: Template: JSON data format</title><link>http://www.codeplex.com/NBusiness/WorkItem/View.aspx?WorkItemId=15361</link><description>Output code handlers that can be queried against by a web application using Javascript JSON data format.  This would entail returning the data in JSON fashion, just like getting the object&amp;#39;s xml using the EntityInfoBase etc.   Basically the handller should output JSON like&amp;#58;&lt;br /&gt;&lt;br /&gt;JSONStream ouput &amp;#61; &amp;#60;Handlers&amp;#62;.Blog.Fetch&amp;#40;0&amp;#41; &amp;#59;&lt;br /&gt;&lt;br /&gt;OR&lt;br /&gt;&lt;br /&gt;JSONStream output &amp;#61; Blog.Fetch&amp;#40;0&amp;#41;.toJSON&amp;#40;&amp;#41;&amp;#59;  &amp;#40;then leave the implementation up to the developer&amp;#41;&lt;br /&gt;</description><author>kleneau</author><pubDate>Wed, 27 Feb 2008 17:19:11 GMT</pubDate><guid isPermaLink="false">CREATED ISSUE: Template: JSON data format 20080227051911P</guid></item><item><title>COMMENTED ISSUE: XML generation error in Schema Updater</title><link>http://www.codeplex.com/NBusiness/WorkItem/View.aspx?WorkItemId=15037</link><description>When trying to save the database connection string I get the error &amp;#34;There was an error generating the XML document&amp;#34;.  I am able to test the connection and it succeeds, but when I try to save it it closes the window and this error pops up.  When i click &amp;#34;update&amp;#34; the database connection window pops up and I get the same error when trying to save.&lt;br /&gt;&lt;br /&gt;I was able to fix this before with some combination of closing visual studio and moving the project around, but now that isn&amp;#39;t helping.&lt;br /&gt;Comments: ** Comment from web user: justinc ** &lt;p&gt;This is a very peculiar bug I&amp;#39;ve encountered related to XML serialization and multiple assemblies being loaded of the same type into Visual Studio. Very tricky to get right apparently, I&amp;#39;ll have to just switch it to use the XML document since this is so unstable. This feature, however, is simply opening up the file &amp;#34;&amp;#36;&amp;#40;ProjectDirectory&amp;#41;&amp;#92;obj&amp;#92;Generated&amp;#92;SqlScriptsTemplate&amp;#92;complete.sql&amp;#34; and executing it on the database you specified.&lt;/p&gt;&lt;p&gt;A work around is to simply open this file with Sql Server management studio and execute it that way.&lt;/p&gt;</description><author>justinc</author><pubDate>Mon, 18 Feb 2008 18:27:25 GMT</pubDate><guid isPermaLink="false">COMMENTED ISSUE: XML generation error in Schema Updater 20080218062725P</guid></item><item><title>COMMENTED ISSUE: XML generation error in Schema Updater</title><link>http://www.codeplex.com/NBusiness/WorkItem/View.aspx?WorkItemId=15037</link><description>When trying to save the database connection string I get the error &amp;#34;There was an error generating the XML document&amp;#34;.  I am able to test the connection and it succeeds, but when I try to save it it closes the window and this error pops up.  When i click &amp;#34;update&amp;#34; the database connection window pops up and I get the same error when trying to save.&lt;br /&gt;&lt;br /&gt;I was able to fix this before with some combination of closing visual studio and moving the project around, but now that isn&amp;#39;t helping.&lt;br /&gt;Comments: ** Comment from web user: justinc ** &lt;p&gt;Thanks for the notification. Which version are you using&amp;#63; I&amp;#39;ll check it out.&lt;/p&gt;</description><author>justinc</author><pubDate>Wed, 06 Feb 2008 00:48:48 GMT</pubDate><guid isPermaLink="false">COMMENTED ISSUE: XML generation error in Schema Updater 20080206124848A</guid></item><item><title>CREATED ISSUE: XML generation error in Schema Updater</title><link>http://www.codeplex.com/NBusiness/WorkItem/View.aspx?WorkItemId=15037</link><description>When trying to save the database connection string I get the error &amp;#34;There was an error generating the XML document&amp;#34;.  I am able to test the connection and it succeeds, but when I try to save it it closes the window and this error pops up.  When i click &amp;#34;update&amp;#34; the database connection window pops up and I get the same error when trying to save.&lt;br /&gt;&lt;br /&gt;I was able to fix this before with some combination of closing visual studio and moving the project around, but now that isn&amp;#39;t helping.&lt;br /&gt;</description><author>GrantB</author><pubDate>Mon, 04 Feb 2008 17:17:06 GMT</pubDate><guid isPermaLink="false">CREATED ISSUE: XML generation error in Schema Updater 20080204051706P</guid></item><item><title>CLOSED ISSUE: ObjectDataReader won't read strings</title><link>http://www.codeplex.com/NBusiness/WorkItem/View.aspx?WorkItemId=14421</link><description>There is a bug in the ObjectDataReader where it won&amp;#39;t read a string properly because it incorrectly thinks it&amp;#39;s DBNull.&lt;br /&gt;</description><author>justinc</author><pubDate>Sun, 16 Dec 2007 21:26:24 GMT</pubDate><guid isPermaLink="false">CLOSED ISSUE: ObjectDataReader won't read strings 20071216092624P</guid></item><item><title>COMMENTED ISSUE: ObjectDataReader won't read strings</title><link>http://www.codeplex.com/NBusiness/WorkItem/View.aspx?WorkItemId=14421</link><description>There is a bug in the ObjectDataReader where it won&amp;#39;t read a string properly because it incorrectly thinks it&amp;#39;s DBNull.&lt;br /&gt;Comments: ** Comment from web user: justinc ** &lt;p&gt;fixed in v2.1&lt;/p&gt;</description><author>justinc</author><pubDate>Sun, 16 Dec 2007 21:25:47 GMT</pubDate><guid isPermaLink="false">COMMENTED ISSUE: ObjectDataReader won't read strings 20071216092547P</guid></item><item><title>REOPENED ISSUE: ObjectDataReader won't read strings</title><link>http://www.codeplex.com/NBusiness/WorkItem/View.aspx?WorkItemId=14421</link><description>There is a bug in the ObjectDataReader where it won&amp;#39;t read a string properly because it incorrectly thinks it&amp;#39;s DBNull.&lt;br /&gt;Comments: ** Comment from web user: justinc ** &lt;p&gt;changing to v2.1&lt;/p&gt;</description><author>justinc</author><pubDate>Sun, 16 Dec 2007 21:25:27 GMT</pubDate><guid isPermaLink="false">REOPENED ISSUE: ObjectDataReader won't read strings 20071216092527P</guid></item><item><title>COMMENTED ISSUE: ObjectDataReader won't read strings</title><link>http://www.codeplex.com/NBusiness/WorkItem/View.aspx?WorkItemId=14421</link><description>There is a bug in the ObjectDataReader where it won&amp;#39;t read a string properly because it incorrectly thinks it&amp;#39;s DBNull.&lt;br /&gt;Comments: ** Comment from web user: justinc ** &lt;p&gt;&lt;/p&gt;&lt;p&gt;&amp;#42;&amp;#42; Closed by justinc 12&amp;#47;16&amp;#47;2007 12&amp;#58;43 PM&lt;/p&gt;</description><author>justinc</author><pubDate>Sun, 16 Dec 2007 21:25:27 GMT</pubDate><guid isPermaLink="false">COMMENTED ISSUE: ObjectDataReader won't read strings 20071216092527P</guid></item><item><title>CLOSED ISSUE: ObjectDataReader won't read strings</title><link>http://www.codeplex.com/NBusiness/WorkItem/View.aspx?WorkItemId=14421</link><description>There is a bug in the ObjectDataReader where it won&amp;#39;t read a string properly because it incorrectly thinks it&amp;#39;s DBNull.&lt;br /&gt;</description><author>justinc</author><pubDate>Sun, 16 Dec 2007 20:43:16 GMT</pubDate><guid isPermaLink="false">CLOSED ISSUE: ObjectDataReader won't read strings 20071216084316P</guid></item><item><title>CREATED ISSUE: ObjectDataReader won't read strings</title><link>http://www.codeplex.com/NBusiness/WorkItem/View.aspx?WorkItemId=14421</link><description>There is a bug in the ObjectDataReader where it won&amp;#39;t read a string properly because it incorrectly thinks it&amp;#39;s DBNull.&lt;br /&gt;</description><author>justinc</author><pubDate>Sun, 16 Dec 2007 20:03:20 GMT</pubDate><guid isPermaLink="false">CREATED ISSUE: ObjectDataReader won't read strings 20071216080320P</guid></item><item><title>COMMENTED FEATURE: Allow multiple database providers</title><link>http://www.codeplex.com/NBusiness/WorkItem/View.aspx?WorkItemId=12962</link><description>I could be that a given application has multiple NBusiness projects with it. It could be that each project needs a different configuration. Maybe one of them needs to go to sql and one goes to an XML database provider. Also allow configurations to be made per entity. For example&amp;#58;&lt;br /&gt;&lt;br /&gt;&amp;#123;&amp;#123;&lt;br /&gt;&amp;#60;NBusiness AuthorizeDefault&amp;#61;&amp;#34;false&amp;#34; AccessDefault&amp;#61;&amp;#34;true&amp;#34; &amp;#62;&lt;br /&gt;    &amp;#60;Assemblies&amp;#62;&lt;br /&gt;        &amp;#60;Add Assembly&amp;#61;&amp;#34;Test1.Business&amp;#34; Provider&amp;#61;&amp;#34;NBusiness.Providers.SqlDatabaseProvider, NBusiness&amp;#34; AuthorizeDefault&amp;#61;&amp;#34;true&amp;#34; &amp;#47;&amp;#62;&lt;br /&gt;        &amp;#60;Add Assembly&amp;#61;&amp;#34;Test2.Business&amp;#34; Provider&amp;#61;&amp;#34;NBusiness.Providers.XmlDatabaseProvider &amp;#47;&amp;#62;&lt;br /&gt;    &amp;#60;&amp;#47;Assemblies&amp;#62;&lt;br /&gt;    &amp;#60;Types&amp;#62;&lt;br /&gt;        &amp;#60;Add Type&amp;#61;&amp;#34;Test1.Business.TestEntity, Test1.Business&amp;#34; Provider&amp;#61;&amp;#34;exampleprovider&amp;#34; &amp;#47;&amp;#62;&lt;br /&gt;    &amp;#60;&amp;#47;Types&amp;#62;&lt;br /&gt;&amp;#60;&amp;#47;NBusiness&amp;#62;&lt;br /&gt;&amp;#125;&amp;#125;&lt;br /&gt;&lt;br /&gt;The defaults get assigned in the NBusiness tag like normal, assembly or type level options may be set in addition to that. When getting an instance of the NBusiness configuration the callers type must be passed in now, like&amp;#58;&lt;br /&gt;&lt;br /&gt;NBusiness.Data.Settings.GetInstance&amp;#40;this.GetType&amp;#40;&amp;#41;&amp;#41;.Database.Fetch&amp;#40; ... &amp;#41;&amp;#59;&lt;br /&gt;Comments: Associated with changeset 29067.</description><author>justinc</author><pubDate>Sat, 08 Dec 2007 17:13:51 GMT</pubDate><guid isPermaLink="false">COMMENTED FEATURE: Allow multiple database providers 20071208051351P</guid></item><item><title>CLOSED ISSUE: Sibling Relationship Naming conflict</title><link>http://www.codeplex.com/NBusiness/WorkItem/View.aspx?WorkItemId=13442</link><description>Calling one entity Product and another one ProductColor and assigning a sibling relationship between them will cause a compile error with the message &amp;#34;&amp;#34;An item with the same key has already been added.&amp;#34; This is undoubtedly due to a dictionary using the names of the entities and relationships incorrectly to create the same dictionary key twice and blowing up. Find out where it is happening and make the dictionary keys more unique.&lt;br /&gt;</description><author>justinc</author><pubDate>Sat, 08 Dec 2007 17:13:51 GMT</pubDate><guid isPermaLink="false">CLOSED ISSUE: Sibling Relationship Naming conflict 20071208051351P</guid></item><item><title>COMMENTED FEATURE: Dynamic Sql Queries</title><link>http://www.codeplex.com/NBusiness/WorkItem/View.aspx?WorkItemId=13556</link><description>Create an object model for building dynamic sql queries.&lt;br /&gt;Comments: Associated with changeset 29067.</description><author>justinc</author><pubDate>Sat, 08 Dec 2007 17:13:49 GMT</pubDate><guid isPermaLink="false">COMMENTED FEATURE: Dynamic Sql Queries 20071208051349P</guid></item><item><title>CLOSED FEATURE: Validation Warnings</title><link>http://www.codeplex.com/NBusiness/WorkItem/View.aspx?WorkItemId=13343</link><description>Allow validation rules to report as warnings or errors instead of just as errors. If a rule reports as a warning it will count as a broken rule but IsValid will return true.&lt;br /&gt;</description><author>justinc</author><pubDate>Sat, 08 Dec 2007 07:01:54 GMT</pubDate><guid isPermaLink="false">CLOSED FEATURE: Validation Warnings 20071208070154A</guid></item><item><title>CLOSED FEATURE: Allow multiple database providers</title><link>http://www.codeplex.com/NBusiness/WorkItem/View.aspx?WorkItemId=12962</link><description>I could be that a given application has multiple NBusiness projects with it. It could be that each project needs a different configuration. Maybe one of them needs to go to sql and one goes to an XML database provider. Also allow configurations to be made per entity. For example&amp;#58;&lt;br /&gt;&lt;br /&gt;&amp;#123;&amp;#123;&lt;br /&gt;&amp;#60;NBusiness AuthorizeDefault&amp;#61;&amp;#34;false&amp;#34; AccessDefault&amp;#61;&amp;#34;true&amp;#34; &amp;#62;&lt;br /&gt;    &amp;#60;Assemblies&amp;#62;&lt;br /&gt;        &amp;#60;Add Assembly&amp;#61;&amp;#34;Test1.Business&amp;#34; Provider&amp;#61;&amp;#34;NBusiness.Providers.SqlDatabaseProvider, NBusiness&amp;#34; AuthorizeDefault&amp;#61;&amp;#34;true&amp;#34; &amp;#47;&amp;#62;&lt;br /&gt;        &amp;#60;Add Assembly&amp;#61;&amp;#34;Test2.Business&amp;#34; Provider&amp;#61;&amp;#34;NBusiness.Providers.XmlDatabaseProvider &amp;#47;&amp;#62;&lt;br /&gt;    &amp;#60;&amp;#47;Assemblies&amp;#62;&lt;br /&gt;    &amp;#60;Types&amp;#62;&lt;br /&gt;        &amp;#60;Add Type&amp;#61;&amp;#34;Test1.Business.TestEntity, Test1.Business&amp;#34; Provider&amp;#61;&amp;#34;exampleprovider&amp;#34; &amp;#47;&amp;#62;&lt;br /&gt;    &amp;#60;&amp;#47;Types&amp;#62;&lt;br /&gt;&amp;#60;&amp;#47;NBusiness&amp;#62;&lt;br /&gt;&amp;#125;&amp;#125;&lt;br /&gt;&lt;br /&gt;The defaults get assigned in the NBusiness tag like normal, assembly or type level options may be set in addition to that. When getting an instance of the NBusiness configuration the callers type must be passed in now, like&amp;#58;&lt;br /&gt;&lt;br /&gt;NBusiness.Data.Settings.GetInstance&amp;#40;this.GetType&amp;#40;&amp;#41;&amp;#41;.Database.Fetch&amp;#40; ... &amp;#41;&amp;#59;&lt;br /&gt;</description><author>justinc</author><pubDate>Sat, 08 Dec 2007 03:57:21 GMT</pubDate><guid isPermaLink="false">CLOSED FEATURE: Allow multiple database providers 20071208035721A</guid></item><item><title>COMMENTED FEATURE: MySql provider</title><link>http://www.codeplex.com/NBusiness/WorkItem/View.aspx?WorkItemId=12865</link><description>Create a database provider and script template for MySql&lt;br /&gt;Comments: Associated with changeset 29063.</description><author>justinc</author><pubDate>Sat, 08 Dec 2007 03:57:20 GMT</pubDate><guid isPermaLink="false">COMMENTED FEATURE: MySql provider 20071208035720A</guid></item></channel></rss>