<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="/rss.xsl"?><rss version="2.0"><channel><title>AppArch Forum Rss Feed</title><link>http://www.codeplex.com/AppArch/Thread/List.aspx</link><description>AppArch Forum Rss Description</description><item><title>New Post: Is this project keep updating?</title><link>http://apparch.codeplex.com/discussions/440276</link><description>&lt;div style="line-height: normal;"&gt;Is this project keep updating?&lt;br /&gt;
Where is the newest info?&lt;br /&gt;
&lt;/div&gt;</description><author>VictorWoo</author><pubDate>Mon, 15 Apr 2013 02:24:03 GMT</pubDate><guid isPermaLink="false">New Post: Is this project keep updating? 20130415022403A</guid></item><item><title>New Post: Is this project keep updating?</title><link>http://apparch.codeplex.com/discussions/440275</link><description>&lt;div style="line-height: normal;"&gt;Is this project keep updating?&lt;br /&gt;
Where is the newest info?&lt;br /&gt;
&lt;/div&gt;</description><author>VictorWoo</author><pubDate>Mon, 15 Apr 2013 02:24:01 GMT</pubDate><guid isPermaLink="false">New Post: Is this project keep updating? 20130415022401A</guid></item><item><title>New Post: Some questions regarding definitions and where to put use case implementation.</title><link>http://apparch.codeplex.com/discussions/428783</link><description>&lt;div style="line-height: normal;"&gt;Hi Peter,&lt;br /&gt;
&lt;br /&gt;
Have you got answers to your questions? If so can you share it with me. I have pretty much similar questions in my mind. &lt;br /&gt;
&lt;br /&gt;
Thanks&lt;br /&gt;
&lt;/div&gt;</description><author>fahadjaved</author><pubDate>Sat, 13 Apr 2013 20:29:06 GMT</pubDate><guid isPermaLink="false">New Post: Some questions regarding definitions and where to put use case implementation. 20130413082906P</guid></item><item><title>New Post: Some questions regarding definitions and where to put use case implementation.</title><link>http://apparch.codeplex.com/discussions/428783</link><description>&lt;div style="line-height: normal;"&gt;
&lt;p&gt;Dear App Arch Guide team,&lt;/p&gt;
&lt;p&gt;I read most of the &amp;ldquo;Microsoft Application Architecture Guide 2&lt;sup&gt;nd&lt;/sup&gt; Edition&amp;rdquo;, with emphasis on the first 14 chapters, where my following questions refer to. At first I want to thank you (and the many other contributors) for the great
 guide, it already helped me very much in finding out how to structure my layers (together with the Layered Architecture Sample by Serena Yeoh). I posted my questions on stackoverflow.com some days ago (because the discussion site on codeplex seemed not to
 be active any more), but it was closed as &amp;ldquo;too vague&amp;rdquo; (not my opinion, of course). Since my main objective is to get a qualified answer, I wanted to ask you kindly whether you could help me; if not directly, feel free to forward this to any of
 your co-authors if more specialised on this topic. I expanded the list of questions now to all which popped up to me during reading of the guide. I know they are many, but I hope they are interesting feedback for you, too.&lt;/p&gt;
&lt;p&gt;Many thanks in advance for any help and again for this great guide!&lt;/p&gt;
&lt;p&gt;Acronyms used by me:&lt;/p&gt;
&lt;p&gt;Application logic (AL)&lt;/p&gt;
&lt;p&gt;Business logic (BL)&lt;/p&gt;
&lt;p&gt;Domain logic (DL)&lt;/p&gt;
&lt;p&gt;Business components (BCs)&lt;/p&gt;
&lt;p&gt;business workflow components (BWCs)&lt;/p&gt;
&lt;p&gt;business process components (BPCs)&lt;/p&gt;
&lt;p&gt;business entities (BEs)&lt;/p&gt;
&lt;p&gt;business logic components (BLCs)&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;span style="font-size:7pt"&gt;&amp;nbsp;&lt;/span&gt;What exactly are BPCs, how do they differ from BEs, as both implement business logic: &amp;ldquo;Chapter 10: Component Guidelines&amp;rdquo; &amp;gt; Business Layer Components: BWCs: &amp;ldquo;&amp;hellip;the application can use this
 to perform a business process&amp;hellip;&amp;rdquo;, &amp;ldquo;BWCs work with BPCs that instantiate and perform operations on BWCs.&amp;rdquo; BEs: &amp;ldquo;BEs, or &amp;ndash; more generally &amp;ndash; business objects, encapsulate the business logic&amp;hellip;&amp;rdquo;.&lt;br&gt;
This question seems to have something to do with &amp;ldquo;application state&amp;rdquo; vs. &amp;ldquo;entity (domain object) state&amp;rdquo; and how to differentiate between these two. Could you provide some examples for each of the two, since I have only a vague imagination
 what the differences could be? &lt;/li&gt;&lt;li&gt;&lt;span style="font-size:7pt"&gt;&amp;nbsp;&lt;/span&gt;Are BCs the general term for business workflow components (BWCs), business process components (BPCs), business entities (BEs), utility classes etc., as suggested in Chapter 12: &amp;ldquo;Designing Business Entities&amp;rdquo;
 (&amp;ldquo;Examples of these components include business logic components, business entities, business process or workflow components, and utility and helper components&amp;rdquo;) or are they all EXCLUDING the BWCs and BEs, as suggested by the layer diagram e.g.
 on page 84, where they are depicted separately? Or are there two different definitions of BCs used here, one like in chapter 12 where BWCs and BEs are included and the other like in Chapter 14, Step 5 &amp;ldquo;Design BCs to support Workflow&amp;rdquo; where they
 are separated from BWCs in the context of BizTalk Server like in the layer diagram?
&lt;/li&gt;&lt;li&gt;Contradictory definitions of term BLCs:&amp;nbsp; In chapter 10: &amp;ldquo;Component Guidelines&amp;rdquo; &amp;gt; &amp;ldquo;Business Layer Components&amp;rdquo;, BLCs are defined as encompassing BWCs (and also BPCs? Please see question 1 and clarify.) and BEs. However, in
 chapter 12: &amp;ldquo;Designing BCs&amp;rdquo; &amp;gt; &amp;ldquo;Step 1 &amp;ndash; Identify BCs Your Application Will Use&amp;rdquo;, they are not (listed on the same level as BEs and BWCs instead). So which definition is the correct one?
&lt;/li&gt;&lt;li&gt;Same section in chapter 10 as in question 3: &amp;ldquo;Application logic&amp;rdquo; (AL) vs. &amp;ldquo;business logic&amp;rdquo; (BL): &amp;ldquo;Business logic is defined as any application logic&amp;hellip;&amp;rdquo; i.e. in this definition AL is the more general term. This however
&lt;strong&gt;contradicts Randy Stafford&amp;rsquo;s&lt;/strong&gt; &lt;strong&gt;definition in Fowlers book&lt;/strong&gt; which is: &amp;quot;&lt;strong&gt;Business logic&lt;/strong&gt;&amp;quot; is the
&lt;strong&gt;general term&lt;/strong&gt;, can be subdivided into &lt;strong&gt;&amp;quot;domain logic&amp;quot;&lt;/strong&gt; (purely concerned with the problem domain) and
&lt;strong&gt;&amp;quot;application logic&amp;quot; (&lt;/strong&gt;&lt;em&gt;&amp;ldquo;sometimes referred to as &amp;ldquo;&lt;strong&gt;workflow logic&lt;/strong&gt;&amp;rdquo;, although
&lt;strong&gt;different people have different interpretations of &amp;ldquo;workflow&amp;rdquo;&lt;/strong&gt;.&amp;rdquo;&lt;/em&gt;). (see
&lt;em&gt;Fowler, &amp;quot;Patterns of Enterprise Application Architecture&amp;quot; &amp;gt; &amp;quot;Service Layer&amp;quot;&lt;/em&gt;). Could you be more precise what you mean with AL and tell me what is AL which is not BL (being a subset of it in your definition)?
&lt;/li&gt;&lt;li&gt;Same section: &amp;ldquo;&lt;strong&gt;business logic components should not contain any behaviour or application logic that is specific to a use case or user story.
&lt;/strong&gt;BLCs can be further subdivided into the following two components (BWCs and BECs)&lt;strong&gt;&amp;rdquo;.
&lt;/strong&gt;So where do I implement the use cases? &amp;ldquo;It depends? J&amp;rdquo; In the article cited in question 4, Randy Stafford writes: &amp;ldquo;In the
&lt;strong&gt;operation script&lt;/strong&gt; approach a Service Layer is implemented as a set of thicker classes (&amp;ldquo;services&amp;rdquo;) that
&lt;strong&gt;directly implement application logic&lt;/strong&gt; but &lt;strong&gt;delegate&lt;/strong&gt; to encapsulated
&lt;strong&gt;domain object classes&lt;/strong&gt; for &lt;strong&gt;domain logic&lt;/strong&gt;&amp;rdquo;. I think this is the approach followed in the &amp;ldquo;Layered Architecture Sample&amp;rdquo; by Serena Yeoh, i.e. the use cases are in the service layer?
&lt;/li&gt;&lt;li&gt;Finally: I always thought &amp;ldquo;workflow&amp;rdquo; and &amp;ldquo;use cases&amp;rdquo; were somewhat related? I did nowhere find something about how these terms relate (or do not) to each other. Could you explain that to me a) in general, b) specifically concerning
 MS Workflow Foundation? &lt;/li&gt;&lt;/ol&gt;
&lt;p&gt;Many thanks for your patience if you read this far,&lt;/p&gt;
&lt;p&gt;Peter.&lt;/p&gt;
&lt;/div&gt;</description><author>atemoya</author><pubDate>Mon, 07 Jan 2013 16:10:39 GMT</pubDate><guid isPermaLink="false">New Post: Some questions regarding definitions and where to put use case implementation. 20130107041039P</guid></item><item><title>New Post: Updates</title><link>http://apparch.codeplex.com/discussions/260589</link><description>&lt;div style="line-height: normal;"&gt;
&lt;p&gt;Are any further updates planned for this site?&lt;/p&gt;
&lt;/div&gt;</description><author>m4tthall</author><pubDate>Wed, 08 Jun 2011 09:10:54 GMT</pubDate><guid isPermaLink="false">New Post: Updates 20110608091054A</guid></item><item><title>New Post: Is Web Architecture Pocket Guide a subset of App Arch Guide?</title><link>http://apparch.codeplex.com/Thread/View.aspx?ThreadId=230144</link><description>&lt;div style="line-height: normal;"&gt;&lt;p&gt;Is Web Architecture Pocket Guide a subset of App Arch Guide?&lt;/p&gt;&lt;/div&gt;</description><author>fujiy</author><pubDate>Fri, 08 Oct 2010 11:45:31 GMT</pubDate><guid isPermaLink="false">New Post: Is Web Architecture Pocket Guide a subset of App Arch Guide? 20101008114531A</guid></item><item><title>New Post: Error message to be displayed to the user</title><link>http://apparch.codeplex.com/Thread/View.aspx?ThreadId=78875</link><description>&lt;div style="line-height: normal;"&gt;&lt;p&gt;The document has been really helpful, thank you.&lt;/p&gt;
&lt;p&gt;One area that I have not been able to find much information on, beyond exception handling, is handing error messages. And when I say error message, I mean the message that at the highest level is displayed to the user. I want to store these messages in a central location, but I am not sure the best method of doing so.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I am currently working on an ASP.NET MVC site, and I could place all the error message in the controllers to be passed to the UI. It seems it would be better if all these error message and their content were in one central location. Maybe an ENUM would be well suited here, but then it has to be customized to be able to handle the string text of the message, so it does not feel natural.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I am looking for some different input here, and how others may have done this.&amp;nbsp;&lt;/p&gt;&lt;/div&gt;</description><author>rbware83</author><pubDate>Tue, 22 Dec 2009 21:59:06 GMT</pubDate><guid isPermaLink="false">New Post: Error message to be displayed to the user 20091222095906P</guid></item><item><title>New Post: Scalenet.pdf update planned?</title><link>http://apparch.codeplex.com/Thread/View.aspx?ThreadId=53420</link><description>&lt;div style="line-height: normal;"&gt;Is there any planned update for scalenet.pdf (Improving .NET Application Performance and Scalability)at &lt;a href="http://msdn.microsoft.com/en-us/library/ms998530.aspx"&gt;http://msdn.microsoft.com/en-us/library/ms998530.aspx&lt;/a&gt;?  This came out in 2004.  While it is still useful, it is hard to use it as a reference in performance and architecture discussions without being challenged that we're 3 levels later on .Net Framework since then.&lt;br&gt;
&lt;br&gt;
Regards,&lt;br&gt;
&lt;br&gt;
Dale&lt;br&gt;
&lt;/div&gt;</description><author>dalepres</author><pubDate>Wed, 15 Apr 2009 21:17:41 GMT</pubDate><guid isPermaLink="false">New Post: Scalenet.pdf update planned? 20090415091741P</guid></item><item><title>New Post: Durable Services for Mobile</title><link>http://apparch.codeplex.com/Thread/View.aspx?ThreadId=52998</link><description>&lt;div style="line-height: normal;"&gt;&lt;span style="font-family:calibri"&gt;
&lt;p style="text-align:left"&gt;This document states: &lt;br&gt;
If you need durable state, you can use the durable storage (introduced in .NET 3.5) or implement your own custom solution.&lt;br&gt;
&lt;br&gt;
If this is referring to WCF Durable Services here (not durable storage) then this is not so simple to support in the Mobile client since you can't use context-aware bindings OOB. You would have to roll your own client implementation to get this done. I suggest that if this document is to suggest an implementation, it would be good for readers to know what is supported OOB and what is &amp;quot;roll your own&amp;quot;. Otherwise we could be guiding people to think that things are supported as they are for rich clients. Just a suggestion.&lt;/p&gt;
&lt;/span&gt;
&lt;/div&gt;</description><author>dasblonde</author><pubDate>Sat, 11 Apr 2009 19:09:20 GMT</pubDate><guid isPermaLink="false">New Post: Durable Services for Mobile 20090411070920P</guid></item><item><title>New Post: WS-ReliableMessaging Support for Mobile?</title><link>http://apparch.codeplex.com/Thread/View.aspx?ThreadId=52997</link><description>&lt;div style="line-height: normal;"&gt;This document states: &lt;br&gt;
&lt;span style="font-family:calibri"&gt;You can use WS-Reliable Messaging to implement reliable end-to-end communication, even when one or more Web services intermediaries must be traversed.&lt;br&gt;
&lt;br&gt;
I don't think that WS-RM is supported for mobile, since we can't use WSHttpBinding. Unless you want to roll your own WS-RM protocol.&lt;br&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;/span&gt;
&lt;/div&gt;</description><author>dasblonde</author><pubDate>Sat, 11 Apr 2009 19:05:40 GMT</pubDate><guid isPermaLink="false">New Post: WS-ReliableMessaging Support for Mobile? 20090411070540P</guid></item><item><title>New Post: Silverlight For Mobile Doesn't Exist?</title><link>http://apparch.codeplex.com/Thread/View.aspx?ThreadId=52996</link><description>&lt;div style="line-height: normal;"&gt;My understanding is that Silverlight for Mobile does not exist. Am I wrong? If not, will this document be updated to remove that section?&lt;br&gt;
&lt;/div&gt;</description><author>dasblonde</author><pubDate>Sat, 11 Apr 2009 19:02:51 GMT</pubDate><guid isPermaLink="false">New Post: Silverlight For Mobile Doesn't Exist? 20090411070251P</guid></item><item><title>New Post: Correct Link for Data Access Layer Video</title><link>http://www.codeplex.com/AppArch/Thread/View.aspx?ThreadId=48180</link><description>&lt;div style="line-height: normal;"&gt;&lt;span&gt;The correct link for the Data Access Layer Video is:&lt;br&gt;
http://www.codeplex.com/AppArch/Wiki/View.aspx?title=Video%3a%20Data%20Layer%20Layer&amp;amp;version=3&lt;br&gt;
&lt;/span&gt;
&lt;/div&gt;</description><author>Gooch</author><pubDate>Mon, 23 Feb 2009 02:09:58 GMT</pubDate><guid isPermaLink="false">New Post: Correct Link for Data Access Layer Video 20090223020958A</guid></item><item><title>New Post: Prism - I don't see the pattern...  </title><link>http://www.codeplex.com/AppArch/Thread/View.aspx?ThreadId=45420</link><description>&lt;div style="line-height: normal;"&gt;Probably a poor choice of pun  ;)   Prism effectively utilizes patterns such as Supervising Controller MVP and Separated Presentation.  The point is more towards seeing Silverlight as a fat client than thin, and like patterns, architectures should twist and turn with the times.&lt;br&gt;
&lt;br&gt;
With new and emerging technologies we have to continually revise and twist existing patterns&lt;br&gt;
   + MVC -&amp;gt; MVP&lt;br&gt;
   + ASP.NET MVC (Model2) from MVC &lt;br&gt;
   + Presentation Model from MVC/Application Model. &lt;br&gt;
&lt;br&gt;
Enter stage left Prism (aka CompositeWPF); permitting us to create fat clients on client side with the language we love so much - .NET.    &lt;br&gt;
&lt;br&gt;
The  Presentation -&amp;gt; WCF -&amp;gt; Service Layer -&amp;gt; BLL -&amp;gt; DAL meets conventional programming needs but not for Prism.   With Prism, modules are in different assemblies (which can be loaded dynamically).  To use Silverlight as a simple (but elegant) UI is a waste of client processing power resulting in unnecessary round trips - much of the application business logic can be in our Prism applications keeping our WCF services more generic and reusable across multiple applications, e.g., an Employee service that knows how to get data from numerous corporate application databases and resources such as ADS.&lt;br&gt;
&lt;br&gt;
What became problematic on a recent sprint was the addition of our first module's Web Service.   A problem because there is no SvcUtil.exe for Silverlight (yet) and we are tied to L2S so we are forced to go with &amp;quot;Add Web Service&amp;quot; and as such we can only reference our entities from our data layer (yes, we have a IBLL-&amp;gt;IDataProvider in our silverlight module).  Not to mention it's configuration file; this file coupled with the Website configuration file and the requirement to give the main assembly a copy of the ServiceReferences.ClientConfig (Prism V2 Drop 8) which results in three configurations to maintain for a simple, single module application; this application will grow into a multitude of modules.&lt;br&gt;
&lt;br&gt;
Some may think that three configuration files in itself doesn't seem so bad, but wait until you have to move them through a cycle of Development, Staging and Production servers.   With every new module that accesses WCF Services comes additional configuration files to maintain.&lt;br&gt;
&lt;br&gt;
---  &lt;br&gt;
&lt;br&gt;
In the absence of an authoritative source and guidance (if it's out there I can't find it) the solution I'm toying with is pretty basic - when dealing with a fat client we're taught that you should have a pattern (PresentationModel, MVP, etc) that consumes a reusable service - so it starts to look like this:&lt;br&gt;
&lt;br&gt;
Presenter -&amp;gt; IService -&amp;gt; IBLL -&amp;gt; IDataProvider  ~~~ WCF -&amp;gt; Service layer -&amp;gt; BLL -&amp;gt; DAL&lt;br&gt;
&lt;br&gt;
Where the IService, IBLL and IDataProvider are configured in the application's Unity configuration section.   Unfortunately with &amp;quot;Add Web Reference&amp;quot; we can only reference our entities from the implementation of our IDataProvider so I'm researching the fastest method to project the results into a Shared library entities; this way our IService and IBLL are oblivious (as they should be) to the data object model - for example if I want to have my IDataProvider dynamically set to an implementation that operates from an Isolated Storage data file if available.&lt;br&gt;
&lt;br&gt;
Any guidance from the gurus on this matter would be appreciated.   &lt;br&gt;
&lt;/div&gt;</description><author>Billkrat</author><pubDate>Tue, 27 Jan 2009 22:20:21 GMT</pubDate><guid isPermaLink="false">New Post: Prism - I don't see the pattern...   20090127102021P</guid></item><item><title>New Post: New type of solutions</title><link>http://www.codeplex.com/AppArch/Thread/View.aspx?ThreadId=36288</link><description>&lt;div style="line-height: normal;"&gt;Hi plpasta,&lt;br&gt;
   This was beyond the scope of what we examined.  We haven't really brought in any 3rd party frameworks by name with the exception of logging for mobile clients because some of our experts felt it was important enough to give a few examples. We were going for something more timeless. As external frameworks can change and we just recommend &amp;quot;3rd party&amp;quot; solutions in certain cases or ignored the issue in favor of stating the principles that a framework should utilize. We didn't want to refer to much in print. We often even pass over our own offerings, leaving them at the bottom as reference and out of the main principles. &lt;br&gt;
&lt;br&gt;
But, we do recognize the power there. Afterall, we do have our own dependency injection framework (Unity). &lt;br&gt;
&lt;br&gt;
Anyone in the community is welcome to comment the pages where these frameworks are relevant. Just comment the wiki pages on &lt;a href="http://www.codeplex.com/AppArchGuide"&gt;http://www.codeplex.com/AppArchGuide&lt;/a&gt; . &lt;br&gt;
&lt;br&gt;
Rob
&lt;/div&gt;</description><author>rboucher</author><pubDate>Wed, 14 Jan 2009 21:27:06 GMT</pubDate><guid isPermaLink="false">New Post: New type of solutions 20090114092706P</guid></item><item><title>New Post: But what about the database?</title><link>http://www.codeplex.com/AppArch/Thread/View.aspx?ThreadId=39895</link><description>&lt;div style="line-height: normal;"&gt;&lt;p&gt;Thank for the link.  We agree that database design is certainly important.  However at 387 pages, we had to draw the line somewhere. Proper database design is a huge topic in itself.  &lt;br&gt;
I've passed on this feedback to p&amp;amp;p management for either a KB topic on this site or perhaps more guidance in the future. &lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Rob&lt;/p&gt;
&lt;/div&gt;</description><author>rboucher</author><pubDate>Wed, 14 Jan 2009 21:00:29 GMT</pubDate><guid isPermaLink="false">New Post: But what about the database? 20090114090029P</guid></item><item><title>New Post: Where is ASP.NET Model-View-Presenter (MVP)?</title><link>http://www.codeplex.com/AppArch/Thread/View.aspx?ThreadId=41450</link><description>&lt;div style="line-height: normal;"&gt;Hi Chris,&lt;br&gt;
We've certainly mentioned this in the Guide itself and even done videos on it. See the main site &lt;a href="http://www.codeplex.com/AppArch"&gt;http://www.codeplex.com/AppArch&lt;/a&gt; and scroll down to videos.  We haven't covered ASP.NET MVP in depth in the Main guide, other than to mention it, because it's actually too low level for most architectural discussions in the guide.&lt;br&gt;
&lt;br&gt;
Rob
&lt;/div&gt;</description><author>rboucher</author><pubDate>Fri, 09 Jan 2009 23:04:46 GMT</pubDate><guid isPermaLink="false">New Post: Where is ASP.NET Model-View-Presenter (MVP)? 20090109110446P</guid></item><item><title>New Post: Guidance Explorer Online Store</title><link>http://www.codeplex.com/AppArch/Thread/View.aspx?ThreadId=41678</link><description>&lt;div style="line-height: normal;"&gt;Hi Matt,&lt;br&gt;
Sorry we are later on answering this thread.  Yes, this content will go into GE in some form. J.D. Meier, the leader of this project, is actually the inventor of the GE concept.  After the guide is complete, we work on getting the content in GE.  It can sometimes take some time. We've got a new revision of GE out with some bug fixes.&lt;br&gt;
&lt;br&gt;
For those reading this thread who don't know, GE is guidance explorer.  It's a tool used to slice, dice, store, and even modify and edit our content via Rich Client application (or a web version which is less functional than the Rich Client app). Since we write guidance that's highly modular, we can &amp;quot;nuggetize&amp;quot; it the guidance so it fits in the tool. For more information see &lt;a href="http://www.codeplex.com/GuidanceExplorer"&gt;http://www.codeplex.com/GuidanceExplorer&lt;/a&gt; for more information. &lt;br&gt;
&lt;br&gt;
Rob 
&lt;/div&gt;</description><author>rboucher</author><pubDate>Fri, 09 Jan 2009 22:14:03 GMT</pubDate><guid isPermaLink="false">New Post: Guidance Explorer Online Store 20090109101403P</guid></item><item><title>New Post: How about Release via Wiki?</title><link>http://www.codeplex.com/AppArch/Thread/View.aspx?ThreadId=42431</link><description>&lt;div style="line-height: normal;"&gt;The codeplexwiki is on the &lt;a href="http://www.codeplex.com/apparchGuide"&gt;http://www.codeplex.com/apparchGuide&lt;/a&gt; site along with the download of the PDF guide.  It's right on the main page   
&lt;/div&gt;</description><author>rboucher</author><pubDate>Fri, 19 Dec 2008 06:29:21 GMT</pubDate><guid isPermaLink="false">New Post: How about Release via Wiki? 20081219062921A</guid></item><item><title>New Post: How about Release via Wiki?</title><link>http://www.codeplex.com/AppArch/Thread/View.aspx?ThreadId=42431</link><description>&lt;div style="line-height: normal;"&gt;In this case I don't really support anoymous editing, because P&amp;amp;P team is the expert.&lt;br&gt;
&lt;br&gt;
The benefit of Wiki is fast releasing, I don't need to wait for certain amount of time to see next version, but I can always see P&amp;amp;P team's most up-to-date change right away, plus like what you said comments on certain section of article.&lt;br&gt;
&lt;br&gt;
BWT, where is the CodeplexWiki?
&lt;/div&gt;</description><author>hardywang</author><pubDate>Wed, 17 Dec 2008 22:46:23 GMT</pubDate><guid isPermaLink="false">New Post: How about Release via Wiki? 20081217104623P</guid></item><item><title>New Post: How about Release via Wiki?</title><link>http://www.codeplex.com/AppArch/Thread/View.aspx?ThreadId=42431</link><description>&lt;div style="line-height: normal;"&gt;Hi Hardywang,&lt;br&gt;
We do release to Wiki (codeplex wiki) on this site and you can comment on the botom of various pages.  &lt;br&gt;
&lt;br&gt;
What I'm hearing is that you'd like an anonymous wiki like Wikipedia where people can edit the pages themselves? &lt;br&gt;
&lt;br&gt;
Rob
&lt;/div&gt;</description><author>rboucher</author><pubDate>Wed, 17 Dec 2008 22:10:57 GMT</pubDate><guid isPermaLink="false">New Post: How about Release via Wiki? 20081217101057P</guid></item></channel></rss>