How to make changes made to a component be updated immediately

Discussion in 'ASP .Net Building Controls' started by Ingvar Nilsen, Dec 20, 2004.

  1. I have two projects in the same solution.
    One of them contains a component, that is finished, and added to the
    toolbox.

    In the second project I have put this component on the webform.

    The problem arises when I make changes to the component. These changes
    are not immediately recognized in the other project. I rebuild the
    whole solution, doesn't help. I finally found out that if I load
    another solution and the reload the first back again, the component is
    updated, but this is rather cumbersome, a more easy way would be
    appreciated.

    Any suggestions?


    --
    Ingvar Nilsen
     
    Ingvar Nilsen, Dec 20, 2004
    #1
    1. Advertising

  2. "Ingvar Nilsen" <> wrote in message
    news:...
    >I have two projects in the same solution.
    > One of them contains a component, that is finished, and added to the
    > toolbox.
    >
    > In the second project I have put this component on the webform.
    >
    > The problem arises when I make changes to the component. These changes
    > are not immediately recognized in the other project. I rebuild the
    > whole solution, doesn't help. I finally found out that if I load
    > another solution and the reload the first back again, the component is
    > updated, but this is rather cumbersome, a more easy way would be
    > appreciated.
    >
    > Any suggestions?


    It's my understanding that this is an issue with the designers. Basically,
    the designer already has an instance of the old version of the component.
    Even rebuilding the solution doesn't cause the designer to release this
    instance.

    Have you tried doing this with all designers closed? Also, I would think
    that closing the solution and reopening it would work, without opening an
    intermediate solution.

    John Saunders
     
    John Saunders, Dec 20, 2004
    #2
    1. Advertising

  3. John Saunders wrote:
    > Have you tried doing this with all designers closed? Also, I would
    > think that closing the solution and reopening it would work, without
    > opening an intermediate solution.


    Regardless, this is not good RAD (Rapid Application Development).
    Since the VS.Net is made exactly for this, and changes to components
    are made all the time during development, they should be reflected
    immediately, without going through this.

    Hmm. Wonder if there is a way.
    Maybe setting the output path of the component's project to the bin
    folder where the same component is tested would help..

    --
    Ingvar Nilsen
     
    Ingvar Nilsen, Dec 20, 2004
    #3
  4. "Ingvar Nilsen" <> wrote in message
    news:...
    > John Saunders wrote:
    >> Have you tried doing this with all designers closed? Also, I would
    >> think that closing the solution and reopening it would work, without
    >> opening an intermediate solution.

    >
    > Regardless, this is not good RAD (Rapid Application Development).


    No kidding. But try it and find out if this is part of the problem. If so,
    you may find a better way to get around this designer issue. But you'll
    never know if you don't try.

    > Since the VS.Net is made exactly for this, and changes to components
    > are made all the time during development, they should be reflected
    > immediately, without going through this.


    The designers and their infrastructure do not seem to have been given the
    same emphasis as the rest of the Framework. Consider the scant documentation
    for the design-time environment. If Microsoft were to adequately document
    this area and if they were to engage with developers who want to do
    more-sophisticated design-time work, then they might find and fix more of
    these issues sooner.

    In the absence of that, these little "minor" bugs will accumulate.

    > Hmm. Wonder if there is a way.
    > Maybe setting the output path of the component's project to the bin
    > folder where the same component is tested would help..


    It might help at run-time, but consider that even if the runtime environment
    is watching the bin folder (as ASP.NET does), that the design-time
    environment might not watch the bin folder.

    John Saunders
     
    John Saunders, Dec 20, 2004
    #4
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Naveen Kohli

    Tags not updated immediately

    Naveen Kohli, Nov 22, 2004, in forum: ASP .Net Building Controls
    Replies:
    0
    Views:
    103
    Naveen Kohli
    Nov 22, 2004
  2. Ingvar Nilsen

    Adding my component to the right ToolBox tab immediately

    Ingvar Nilsen, Jan 13, 2005, in forum: ASP .Net Building Controls
    Replies:
    0
    Views:
    151
    Ingvar Nilsen
    Jan 13, 2005
  3. Dmitry Korolyov

    Datagrid not updated during delete, but updated during insert and update

    Dmitry Korolyov, Sep 22, 2003, in forum: ASP .Net Datagrid Control
    Replies:
    0
    Views:
    444
    Dmitry Korolyov
    Sep 22, 2003
  4. Hoss
    Replies:
    5
    Views:
    116
    Jonas Raoni
    Feb 23, 2006
  5. iMath
    Replies:
    1
    Views:
    165
    Steven D'Aprano
    Mar 15, 2013
Loading...

Share This Page