AppArch Work Item Rss Feed

Created Issue: The download link seems to be broken... [9446]

gabrielas — Tue, 12 Jun 2012 18:33:27 GMT

Please fix it

Commented Issue: Provide a Reference App or maybe a VS Solution Template

rboucher — Wed, 14 Jan 2009 20:55:28 GMT

ERDA & GBRI are at least 4 years old now...
Comments: ** Comment from web user: rboucher **

We've provided link to reference solutions on this site. See the home page for codeplex.com/apparch. People can also contribute their own at http://www.codeplex.com/apparchcontrib/

We did have the budget to keep going on a full set of reference implementations, though we agree this would be helpful. Perhaps in a later revision.

Closed Issue: Description incorrect for the "Grid" Architecture Style (P29 BETA1 build4)

rboucher — Wed, 14 Jan 2009 20:52:50 GMT

Hey guys,
First, thanks for this great effort. I think it's a good approach to clarify many of the technical aspects in software architecture from Microsoft point of view.
I'm reading the guide start-to-finish and will post in this list whenever something pops up. Hope it works with you guys.

So this particular issue is calling out that in P29, in the Architectural Styles table, the Grid style is not described correctly. The description is presumably for the UI-Grid concept, not the arch style.

Again, great work guys!
Comments: Yes, you are absolutely correct. We removed the Grid reference from this area.

Closed Issue: Communication is misspelled in all the diagrams

rboucher — Wed, 14 Jan 2009 20:50:55 GMT

In the "Cross-Cutting" section of the diagrams, the "Communication" element is spelled with one "m".
Comments: Fixed in the final guide.

Closed Issue: Missing .NET diagram (P49 BETA1 build4)

rboucher — Wed, 14 Jan 2009 20:50:20 GMT

the diagram for the high-level view of the .NET Framework is missing in page 49-50 right after "The following diagram provides
a high-level view of the .NET Framework".
Comments: Fixed in final release of guide. We removed the diagram and reference actually as it wasn't adding as much value as it was taking up page space. IT was just a diagram of the evoluation of .NET. Diagrams like it are available on MSDN or through a google image search.

Closed Issue: Missing bullet for application type (P56 BETA1 build4)

rboucher — Wed, 14 Jan 2009 20:48:34 GMT

the type sentense for Web Applications is missing a bullet in page 56.
Comments: Fixed in final release of guide.

Closed Issue: low quality diagrams (BETA1, build4)

rboucher — Wed, 14 Jan 2009 20:47:59 GMT

there are some low quality diagrams in the PDF version.
Specific application Archtypes diagrams in pages 56-60 are in low quality and difficult to read.

I'll be adding to this issue as I find more low quality diagrams in the document.
Comments: Fixed all low quality diagrams across all guides.

Commented Issue: low quality diagrams (BETA1, build4)

rboucher — Wed, 14 Jan 2009 20:47:32 GMT

Should be fixed at this point.

Created Issue: low quality diagrams (BETA1, build4)

fernandof — Tue, 11 Nov 2008 05:46:34 GMT

Created Issue: Missing bullet for application type (P56 BETA1 build4)

fernandof — Tue, 11 Nov 2008 05:27:08 GMT

the type sentense for Web Applications is missing a bullet in page 56.

Created Issue: Missing .NET diagram (P49 BETA1 build4)

fernandof — Tue, 11 Nov 2008 04:59:48 GMT

the diagram for the high-level view of the .NET Framework is missing in page 49-50 right after "The following diagram provides
a high-level view of the .NET Framework".

Created Issue: Description incorrect for the "Grid" Architecture Style (P29 BETA1 build4)

fernandof — Fri, 07 Nov 2008 04:34:19 GMT

Commented Issue: Communication is misspelled in all the diagrams

rboucher — Fri, 19 Sep 2008 00:23:06 GMT

In the "Cross-Cutting" section of the diagrams, the "Communication" element is spelled with one "m".
Comments: ** Comment from web user: rboucher **

Thanks for the heads up shovavnik. We'll get this fixed as we move forward.

Just to be clear - We'll be doing a typical agile process for continuous improvement. We are going to expose information very early in the process to gain feedback. Well refactor it many times. As such , there may be more misspellings in future. Everthing will get a throughout edit pass before release.

Created Issue: Communication is misspelled in all the diagrams

shovavnik — Thu, 18 Sep 2008 09:46:35 GMT

In the "Cross-Cutting" section of the diagrams, the "Communication" element is spelled with one "m".

Created Issue: Provide a Reference App or maybe a VS Solution Template

adrianporger — Wed, 17 Sep 2008 21:47:27 GMT

ERDA & GBRI are at least 4 years old now...