-----
فعالیتهای این وبلاگ به آدرس زیر منتقل شده است:
فعالیتهای این وبلاگ به آدرس زیر منتقل شده است:
Saturday, September 6, 2008
Saturday, April 12, 2008
چند تا سايت برنامه نويسي ايراني خوب
امروز توي سايتها دنبال چيزي ميگشتم كه متوجه شدم سايتهاي ايراني زيادي راجع به برنامه نويسي و مسائل تكنيكي وجود دارند كه اكثرا كپي پيست يا ترجمه مطالب اوريجينال هستند ولي چند تايي هم هستند كه در نگاه اول محتواي خوبي دارند:
http://barnamenevis.org/forum/index.php
http://www.prdev.com/
http://ce.sharif.edu/~setareh/
http://barnamenevis.org/forum/index.php
http://www.prdev.com/
http://ce.sharif.edu/~setareh/
Monday, April 7, 2008
Acropolis
Project Description
Download All Acropolis Video Series here
Building Rich Client UI With Acropolis
The Acropolis Client Application Framework
Microsoft "code-name" Acropolis, smart client futures
Acropolis is a set of components and tools that make it easier for developers to build and manage modular, business focused, client .NET applications. Acropolis is part of the “.NET Client Futures” wave of releases, our preview of upcoming technologies for Windows client development.
Acropolis builds on the rich capabilities of Microsoft Windows and the .NET Framework, including Windows Presentation Foundation (WPF), by providing tools and pre-built components that help developers quickly assemble applications from loosely-coupled parts and services. With Acropolis you will be able to:
- Quickly create WPF enabled user experiences for your client applications.
- Build client applications from reusable, connectable, modules that allow you to easily create complex, business-focused applications in less time.
- Integrate and host your modules in applications such as Microsoft Office, or quickly build stand-alone client interfaces.
- Change the look and feel of your application quickly using built-in themes, or custom designs using XAML.
- Add features such as workflow navigation and user-specific views with minimal coding.
- Manage, update, and deploy your application modules quickly and easily.
If you read the description above it seems to be very similar to Smart Client Software Factory. What's the relationship between them, how does the future of SCSF looks like? If you have this questions, your planning to use SCSF or you are using SCSF check out this post on Glenn's Block (P&P Product Planner) about P&P, SCSF & Acropolis.
If you wanna play around with Acropolis bits download them from here. For a preview of Acropolis and to get involved I recommend you this video Getting started with code-name "Acropolis".
A New Phase for the Acropolis Project
The Acropolis incubation project has been a great learning experience for us and we have received a lot of great feedback that will keep us very busy for quite a while.
We are very excited to be entering the next phase of the project where we will begin to roll many of the Acropolis concepts into future versions of the .NET Framework for the desktop and Silverlight. Unfortunately, while we figure out exactly how to go about this, we have decided not to release any more Acropolis CTP's. We’re going to keep the current CTP bits available to allow you to continue prototyping and evaluating the Acropolis concepts. There will be no new functionality added to the Acropolis CTPs but we do hope that you will continue to provide feedback to us on what you like or don’t like.
We do have some good news though! We were pleasantly surprised to get feedback from many of you that you want to go live with Acropolis based solutions in the short term. To us that validated a lot of the thinking we have been doing and it is a positive indicator of the Acropolis approach. Because of this type of feedback, we want to help you continue to take advantage of the Acropolis concepts and the power of the .NET platform while we figure out the longer term plan.
We are very excited to announce that we are going to be working closely with the Microsoft Patterns & Practices team to provide guidance (samples, applications blocks, patterns and so on) for building composite client applications for .NET Framework 3.5 and Visual Studio 2008. As part of that effort we want to engage with those that have been following the Acropolis project to ensure that this guidance meets your needs. Glenn Block, the Patterns & Practices client product manager, has much more information about the Composite Applications for Visual Studio 2008 and .NET 3.5 project here. (Click for his post.)
If you have evaluated Acropolis and are unsure whether to adopt it for your project, or to use the existing CAB, or to wait for the new guidance, our guidance for this situation remains the same – if you are building a Windows Forms LOB composite client (with maybe rich islands of WPF content) you should carefully evaluate the current CAB release. If you are specifically interesting in building composite applications on .NET 3.5, please get involved with the Patterns & Practices project and help us to deliver a guidance package that meets your requirements.
Thanks again for your feedback and expect to hear more in the next couple of months about our future plans.
Download All Acropolis Video Series here
Building Rich Client UI With Acropolis
The Acropolis Client Application Framework
Download July CTP Here : http://www.microsoft.com/downloads/details.aspx?FamilyID=44977885-86B5-4AA0-9F20-DB365BFB9D10&displaylang=en
Team Blog : http://blogs.msdn.com/Acropolis/
Reference : http://staff.southworks.net/blogs/johnny/archive/2007/06/06/Microsoft-_2200_code_2D00_name_2200_-Acropolis_2C00_-smart-client-futures.aspx
Sandcastle
Project Description
Sandcastle produces accurate, MSDN style, comprehensive documentation by reflecting over the source assemblies and optionally integrating XML Documentation Comments. Sandcastle has the following key features:
* Works with or without authored comments
* Supports Generics and .NET Framework 2.0
* Sandcastle has 2 main components (MrefBuilder and Build Assembler)
* MrefBuilder generates reflection xml file for Build Assembler
* Build Assembler includes syntax generation, transformation, etc
* Sandcastle is used internally to build .Net Framework documentation
Genereating Website for API documentation using Sandcastle
In this blog on generating builds using Powershell, I provided details on generating a single command wrapper to build CHM and HxS files regardless of where the source assemblies and comments are located. This powershell script provided the following features:
Allows the build options to be read from a configuration file. Options specified on the command line override options defined in the configuration file.
Handles any number of target assemblies and comment files, including globbing.
Handles any number of dependencies.
Should work with .NET 2.0, 3.0, and 3.5.
Supports vs2005, prototype, and Hana presentation styles.
Provides hooks to add new presentation styles in the future, including user defined styles, and user defined function overrides.
The script is written for PowerShell 1.0.
Prerequisites
The build script has the following dependencies:
Latest release of Sandcastle from http://www.codeplex.com/sandcastle.
The DxRoot environment variable must point to the root of the Sandcastle installation.
To make it easier for the user, the PATH environment variable should contain the …/ProductionTools folder, which contains the scbuild.ps1 script.
.NET 2.0 for Sandcastle.
PowerShell 1.0, with the execution policy set to RemoteSigned or Unrestricted. [Note: In a future release we could Authenticode sign the script to make this unnecessary.]
hhc.exe to compile CHM files.
Hxcomp.exe to compile HxS files.
Project Home : http://www.codeplex.com/Sandcastle
Download Here : http://www.codeplex.com/Sandcastle/Release/ProjectReleases.aspx?ReleaseId=9921
Complete State of Project : http://www.codeplex.com/Sandcastle/stats/view
References : http://blogs.msdn.com/sandcastle/ , http://www.codeplex.com/Sandcastle
Sandcastle produces accurate, MSDN style, comprehensive documentation by reflecting over the source assemblies and optionally integrating XML Documentation Comments. Sandcastle has the following key features:
* Works with or without authored comments
* Supports Generics and .NET Framework 2.0
* Sandcastle has 2 main components (MrefBuilder and Build Assembler)
* MrefBuilder generates reflection xml file for Build Assembler
* Build Assembler includes syntax generation, transformation, etc
* Sandcastle is used internally to build .Net Framework documentation
Genereating Website for API documentation using Sandcastle
In this blog on generating builds using Powershell, I provided details on generating a single command wrapper to build CHM and HxS files regardless of where the source assemblies and comments are located. This powershell script provided the following features:
Allows the build options to be read from a configuration file. Options specified on the command line override options defined in the configuration file.
Handles any number of target assemblies and comment files, including globbing.
Handles any number of dependencies.
Should work with .NET 2.0, 3.0, and 3.5.
Supports vs2005, prototype, and Hana presentation styles.
Provides hooks to add new presentation styles in the future, including user defined styles, and user defined function overrides.
The script is written for PowerShell 1.0.
Prerequisites
The build script has the following dependencies:
Latest release of Sandcastle from http://www.codeplex.com/sandcastle.
The DxRoot environment variable must point to the root of the Sandcastle installation.
To make it easier for the user, the PATH environment variable should contain the …/ProductionTools folder, which contains the scbuild.ps1 script.
.NET 2.0 for Sandcastle.
PowerShell 1.0, with the execution policy set to RemoteSigned or Unrestricted. [Note: In a future release we could Authenticode sign the script to make this unnecessary.]
hhc.exe to compile CHM files.
Hxcomp.exe to compile HxS files.
Running the Script
The scbuild.ps1 script can now be used to build a website, in addition to .chm and .hxs files. To build a website use the –BuildWebsite option. For example, to build a website with API documentation for an assembly named test.dll, with comments in comments.xml, use the following command:
scbuild –framework 2.0 –sources test.dll,comments.xml –BuildWebsite
The build result will be in test website. You can use the –name option to specify an output location and root name for the website.
Currently scbuild supports only the default presentation style: -style vs2005. Future versions may support other output styles.
The output from scbuild is designed to be integrated into an existing website. The master page, web.config file, and style sheet in the output directory are intended as a starting point for further customization. You will probably want to keep the contents of the icons and styles directories however, because they are used to give the generated API topics the vs2005 look-and-feel. All JavaScript functionality was disabled in this version, to minimize conflicts with the website the reference topics will be merged into.
Also note the contents of the web.config file, specifically theelement. Make sure to copy the sample definition to your own website, to ensure that non breaking spaces get displayed properly.
The “api” directory contains one ASP.NET content file for each topic and a sitemap that you can merge into the sitemap of an existing website, as shown in the example. At runtime, the sample master page uses a tree view to display the sitemap and a simple content placeholder to display the topics.
To merge the output into your own website, you can copy the api, icons, and styles directories to the target website and include the sitemap into the master sitemap file as appropriate. Or you can use the –WebTemplate option to specify a user defined template that will be copied to the output directory, instead of the Sandcastle sample.
If you want to use the generated sitemap, include the following reference to the API topics in your own sitemap:
Further customization is possible through the –WebBuildConfig option, to specify a custom BuildAssembler config file.
For more information, please refer to the header of the scbuild.ps1 script, which shows a list of all available build options and short descriptions. Hope this helps.
The scbuild.ps1 script can now be used to build a website, in addition to .chm and .hxs files. To build a website use the –BuildWebsite option. For example, to build a website with API documentation for an assembly named test.dll, with comments in comments.xml, use the following command:
scbuild –framework 2.0 –sources test.dll,comments.xml –BuildWebsite
The build result will be in test website. You can use the –name option to specify an output location and root name for the website.
Currently scbuild supports only the default presentation style: -style vs2005. Future versions may support other output styles.
The output from scbuild is designed to be integrated into an existing website. The master page, web.config file, and style sheet in the output directory are intended as a starting point for further customization. You will probably want to keep the contents of the icons and styles directories however, because they are used to give the generated API topics the vs2005 look-and-feel. All JavaScript functionality was disabled in this version, to minimize conflicts with the website the reference topics will be merged into.
Also note the contents of the web.config file, specifically the
The “api” directory contains one ASP.NET content file for each topic and a sitemap that you can merge into the sitemap of an existing website, as shown in the example. At runtime, the sample master page uses a tree view to display the sitemap and a simple content placeholder to display the topics.
To merge the output into your own website, you can copy the api, icons, and styles directories to the target website and include the sitemap into the master sitemap file as appropriate. Or you can use the –WebTemplate option to specify a user defined template that will be copied to the output directory, instead of the Sandcastle sample.
If you want to use the generated sitemap, include the following reference to the API topics in your own sitemap:
For more information, please refer to the header of the scbuild.ps1 script, which shows a list of all available build options and short descriptions. Hope this helps.
Project Home : http://www.codeplex.com/Sandcastle
Download Here : http://www.codeplex.com/Sandcastle/Release/ProjectReleases.aspx?ReleaseId=9921
Complete State of Project : http://www.codeplex.com/Sandcastle/stats/view
References : http://blogs.msdn.com/sandcastle/ , http://www.codeplex.com/Sandcastle
Subscribe to:
Posts (Atom)
