February 2006 - Posts

DotNetNuke is NOT a portal

Many friends ask me that is it DotNetNuke same with other portal engine ?

My answer is NO.

I have made an “Executive Information System” based on DotNetNuke, and that's not a portal. I have made an “Sistem Informasi Sekolah” based on DotNetNuke, and that's not a portal. I have made a payroll application based on DotNetNuke, and that's not a portal. So, i can use to build many other types of applications including standard ASP.NET web applications with DotNetNuke.

DotNetNuke is not a portal. DotNetNuke is a Web Application Framework. You can use the services in the framework to build portals, but you can also use them to build many other types of applications including standard ASP.NET web applications, community sites, intranets, extranets, and vertical market application service provider ( ASP ) applications. In reality, it is a rich service layer on top of ASP.NET which eliminates much of the mundane coding required to build a web application from the ground up.

Check more articles about DotNetNuke on this link : http://blogs.netindonesia.net/agung/category/911.aspx

I will updated a lot of information about DNN on that link. Now i'm prepared for the first release of official site of DotNetNuke Indonesia which comes with a lot of information that you need about DotNetNuke including :

  • How to
  • Articles
  • Skins
  • Modules
  • Audio
  • Video
  • Modified version of DNN that do some spesific task only
  • Consulting
Share this post: | | | |
Posted by agung | with no comments

Try the VSTS in a hosted environment

Check out Rob Caron's post for details.

Share this post: | | | |
Posted by agung | with no comments

Whitehorse Architecture TechNotes Published on MSDN

Phew!  A set of Visual Studio Team System Tech Notes have now been published on MSDN, including some fifteen new articles on topics related to the Whitehorse architecture tools.  These should all be easy to read and are inter-linked, to make them an easy to browse.  Hopefully they will provide some useful background and some new insights into the Distributed System Designers. 

Below are the links, ordered in what is probably a good sequence in which to read them. 

  • TN_1104: Understanding the System Definition Model
  • TN_1114: The Four Layers of Systems in the System Definition Model
  • TN_1100: Understanding Applications and the Application Diagram
  • TN_1105: Why Class Libraries are not shown on an Application Diagram
  • TN_1109: Understanding Systems and the System Designer
  • TN_1101: Understanding and Using the Default System
  • TN_1110: Using Systems to Represent Services in a Service Oriented Architecture
  • TN_1112: System Portfolio Management
  • TN_1102: Designing Substitutable Web Services
  • TN_1113: Representing Connections to Manual, Physical and Other Kinds of System
  • TN_1111: Top-down System Design
  • TN_1108: Connecting Applications to Web Services via Class Libraries
  • TN_1106: Copying Endpoints vs Creating Endpoints from WSDL
  • TN_1103: Web Service Endpoint Name Propagation
  • TN_1107: Understanding, Using and Creating Toolbox Prototypes
  • Why do ASP.NET WebService and ASP.NET WebApplication look alike on the Application Designer? 
  • Share this post: | | | |
    Posted by agung | with no comments

    Add a user control reference

    In (classic) ASP.NET 1.1 you had to reference a user control in every page you wanted to use the control in (@Page-directive).

    ASP.NET 2.0 lightens this work because it allows you to reference heavily used user controls globally in the web.config file.

    When you have added something like this to your web.config:

    <pages>
      <controls>
        <
    add tagPrefix="qd"
             src="~/UI/Controls/ProductList.ascx"
             tagName="ProductList"/>
      </
    controls>
    </
    pages>

    your user control is avaible in every page of your web project accessing it via

    <qd:ProductList ID="qdProductList" runat="Server" />

    And you have full intellisense support for your user control, of course.

    Share this post: | | | |
    Posted by agung | with no comments