Inhoud blog
  • ASP.NET - Asynchronous call to a webservice with impersonation
  • ASP.NET - Custom object as parameter for ObjectDataSource
  • ASP.NET - Identity impersonation
  • MyCalendar - add events without postbacks
  • ASP..NET Web Parts
    Zoeken in blog

    My Profile
  • LinkedIn
  • My Favorite Blogs
  • Kevin DeRudder
  • Rudi Larno
  • David Hayden
  • David Cumps
  • Reinout's blog
    Talking about new features, useful things, frustrations in .NET and so on...
    14-08-2007
    Klik hier om een link te hebben waarmee u dit artikel later terug kunt lezen.ASP..NET Web Parts
    Web Parts are very useful to enable end users to modify the look and feel of your website : the content, appearance and even the behaviour can be changed, this is possible without writing any code.



    First drag a WebPartManager control to the web page. This control must appear before any other Web Part control, otherwise a runtime exception will be thrown (and that's not exactly what we want...)
    Next add WebPartZone controls to the places where you want [an end user] to see Web Parts; you can do this inside a table to get a basic layout. The title can be changed in the HeaderText property.
    You can now start adding (in the design view) some web user controls to the WebPartZone controls by dragging and dropping.

    A quick preview in a browser shows us the controls have a title "Untitled", this can easily be changed by adding title="" in the source code (the intellisense won't recognize it, don't worry about that) :



    Now, all the above is quite useful, but to let the user interact with our web parts, a few things are still missing.
    Add an EditorZone and a CatalogZone the same way as the WebPartZone's above. Make sure not to add them to an existing WebPartZone as this will generate a runtime exception.
    In the EditorZone you can add an AppearanceEditorPart, LayoutEditorPart and BehaviorEditorPart, depending on what you want the end user to do.
    In the CatalogZone you can add a DeclarativeCatalogPart (when you want to add another instance of a predefined user control), a PageCatalogPart (to retain an existing control when you closed it) and an ImportCatalogPart (to import a non-defined user control).

    When taking a quick look in the browser (after building...), you see none of the above appears... This is because the current view is set to the default view : Browse.
    Now let's add a control displaying the different modes, the first code that has to be written (except HTML...) ! (I chose a radiobuttonlist called rbListModes)



    Make sure to set the AutoPostBack property of the control to "true" and start the application. When switching between the different display modes, you will be able to change properties and add/remove controls.
    To edit a control, switch to the Edit mode and click on in the right upper corner of the control and choose "Edit". The Editor parts added to the EditorZone will now become visible.
    To retain a closed control, switch to Catalog mode and navigate to Page Catalog, you will be able to display the control in the WebPartZone of your choice.

    14-08-2007 om 15:45 geschreven door Reinout Waelput  


    Klik hier om een link te hebben waarmee u dit artikel later terug kunt lezen.Uninstall SQL 2005

    Ever had a horrible time trying to remove SQL 2005 (completely) from your system ?

    Here’s the answer :
    http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=354408&SiteID=1

    14-08-2007 om 11:32 geschreven door Reinout Waelput  


    11-08-2007
    Klik hier om een link te hebben waarmee u dit artikel later terug kunt lezen.ASP.NET Error handling

    Error handling is one of the most important (and maybe least enjoying) things to do while developing.

    Most of the times error-prone methods will contain try/catch blocks to prevent the exception from slipping through. There might still be some unhandled exceptions though, in code blocks not "protected" by a try/catch block. Those can be handled on page or on application level.

    Now let's see an example, writing the error to the trace (so it can be viewed and further investigated by a developer using a trace listener) in case of page level error handling and navigating to a user defined error page in case of application level exception handling.

    On page level :

        protected void Page_Error(object sender, EventArgs e)
        {
            // Retrieve the last error and write to the trace
            Trace.Write(Server.GetLastError());
            // Clear the last error
            Server.ClearError();
       
    }

    On application level :

        void Application_Error(object sender, EventArgs e)
        {
            // Navigate to a user defined error page
            Server.Transfer("HandleError.aspx");
            // Make sure to call Server.GetLastError() and Server.ClearError() in the error handling page
       
    }

    11-08-2007 om 23:19 geschreven door Reinout Waelput  


    Klik hier om een link te hebben waarmee u dit artikel later terug kunt lezen.ASP.NET Navigation

    There are different ways to navigate to a different URL, including :
    Response.Redirect(“url”);
    Server.Transfer(“url”, false); 

    What's the difference?
    With Response.Redirect you will not be able to access data from the original page through the PreviousPage property, by using Server.Transfer (or the PostBackUrl property) you will be able to do so.

    11-08-2007 om 23:02 geschreven door Reinout Waelput  


    Klik hier om een link te hebben waarmee u dit artikel later terug kunt lezen.SQL 2005 : get comma separated list
    Ever wanted to return a comma seperated list of values with a query, struggling with functions or cursors ?
    In SQL 2005, there's an easy/short solution for this.

    e.g. to return the name of a company and a comma separated list of e-mail addresses of the users in the company.

    SELECT c.company_name,
            mail = STUFF
                    (
                    (
                        SELECT ‘, ‘ + u.mail_address as [text()]
                          FROM t_User u
                    INNER JOIN t_Company co ON u.company_id = co.company_id
                         WHERE co.company_id = c.company_id
                       FOR XML Path (‘’)
                    ),
                    1,
                    2,
                    ‘’
                    )
      FROM t_Company c

    The STUFF() function removes - in this example - the first 2 characters in the list, to avoid starting the list with a comma followed by a space.
    Text() maps the list to a text node.
    For a description of "FOR XML Path", I refer to the MSDN documentation : http://msdn2.microsoft.com/en-us/library/ms345137.aspx

    11-08-2007 om 21:14 geschreven door Reinout Waelput  


    Klik hier om een link te hebben waarmee u dit artikel later terug kunt lezen.New blog !
    Some people keep asking me when I start blogging again. Yes again, since our first "blogging project" (used to be known as webbullogs) didn't last very long.

    The purpose of this blog is to explain a bit what I'm busy with (mostly .NET related) - which will also allow me to remember some things a little longer ;-) - and some other useful (and at times extremely useless) stuff.

    Hopefully you will enjoy reading it ... and maybe even learn something from it !

    11-08-2007 om 20:33 geschreven door Reinout Waelput  


    27-09-2005
    Klik hier om een link te hebben waarmee u dit artikel later terug kunt lezen.Bringer of silent death

    Neen, uw blog moet niet dagelijks worden bijgewerkt.  Het is gewoon zoals je het zélf wenst.  Indien je geen tijd hebt om dit dagelijks te doen, maar bvb. enkele keren per week, is dit ook goed.  Het is op jouw eigen tempo, met andere woorden: vele keren per dag mag dus ook zeker en vast, 1 keer per week ook.

    Er hangt geen echte verplichting aan de regelmaat.  Enkel is het zo hoe regelmatiger je het blog bijwerkt, hoe meer je bezoekers zullen terugkomen en hoe meer bezoekers je krijgt uiteraard. 

    27-09-2005 om 16:32 geschreven door Reinout Waelput  


    Klik hier om een link te hebben waarmee u dit artikel later terug kunt lezen.JavaScript (more dynamic) slideshow

    Het maken van een blog en het onderhouden is eenvoudig.  Hier wordt uitgelegd hoe u dit dient te doen.

    Als eerste dient u een blog aan te maken- dit kan sinds 2023 niet meer.

    Op die pagina dient u enkele gegevens in te geven. Dit duurt nog geen minuut om dit in te geven. Druk vervolgens op "Volgende pagina".

    Nu is uw blog bijna aangemaakt. Ga nu naar uw e-mail en wacht totdat u van Bloggen.be een e-mailtje heeft ontvangen.  In dat e-mailtje dient u op het unieke internetadres te klikken.

    Nu is uw blog aangemaakt.  Maar wat nu???!

    Lees dit in het volgende bericht hieronder!

    27-09-2005 om 16:32 geschreven door Reinout Waelput  




    Archief per week
  • 03/09-09/09 2007
  • 27/08-02/09 2007
  • 20/08-26/08 2007
  • 13/08-19/08 2007
  • 06/08-12/08 2007
  • 26/09-02/10 2005

    E-mail mij

    Druk op onderstaande knop om mij te e-mailen.



    Blog tegen de wet? Klik hier.
    Gratis blog op https://www.bloggen.be - Meer blogs