Site re-builds all the time, can I stop it? (.NET2 site)

Hi

First off, I am not a programmer and I know less than nothing about asp.

I have had a review database website created that I am told was built using .net2.

I am told by the people that built it that .net2 contains some new feature or something not available on the first one that auto-rebuilds the DB or tree structure(?) everytime something changes to prevent inconsistencies in the DB.

This sounds like a great idea, however my site DB is quite big and so rebuilding all the time causes a small but annoying delay while it rebuilds. Usually about 10 seconds or more. This might not seem like a lot but when it's happening all the time itwill cause my visitors to go elsewhere.

My question is, can I somehow disable this new feature (ideal solution)?

Many thanks

Sitz.

Are you saying your project is being rebuilt? ASP.NET 2.0 does not have a feature where the project is rebuilt when a database is changed. However, ASP.NET 2.0 will rebuild if afile is changed.

Sure need more info on this cause it's nothing I ever heard of.

When you are talking about db or tree structure - what do you mean by that? I.e what kind of database backend are you using?

Firstly, many thanks for both replies.

That sounds like it vcsjones.

Basically when ever I change a review category or approve a review it does the rebuild thing.

e.g. Lets say I have category calledSitruz and I then edit that name and call itSitz. The very next time the site is called it takes 10+ seconds while it goes through and rebuilds the structure.

The exact same thing happens whenever I change reviews or add them.

Once again I sincerely apologise for my vagueness.

No doubt my developers are informing correctly, I just thought it was worth checking on here to see if anyone knows of a way around it that they might not have thought of.

Many thanks

Sitz.

Does anyone have any further thoughts on this?

Please take a look atwww.room2choose.com to get an idea of how my sites working.

Many thanks

Sitz

That's the way it works. The first request for a page after a change recompiles the page and puts it into cache. From there on it comes from cache until it is changed or the cache expires. If the page is requested often enough, the cache won't expire.

Jeff

Sitruz:

Firstly, many thanks for both replies.

That sounds like it vcsjones.

Basically when ever I change a review category or approve a review it does the rebuild thing.

e.g. Lets say I have category calledSitruz and I then edit that name and call itSitz. The very next time the site is called it takes 10+ seconds while it goes through and rebuilds the structure.

The exact same thing happens whenever I change reviews or add them.

Once again I sincerely apologise for my vagueness.

No doubt my developers are informing correctly, I just thought it was worth checking on here to see if anyone knows of a way around it that they might not have thought of.

Many thanks

Sitz.

Well, I don't want to disagree with what others have said here, but it sounds to me like you're not changing a *program* file (ie, aspx, or such), but a data file. What database are you using? SQL 2000? Because it sounds like someone is either feeding you a line (because I see no value in designing something where if you change a *data* value, it recompiles a software program--that's not efficient design AT ALL!), or they haven't explained it so you understand it. I would try to get one of the programmers to come on and explain what's going on.

There is a feature in .NET 2.0 that allows certain files to compile at *run-time*...but it's not something I'd do once the project is complete...especially on a production website...

Aaava,

Thanks for your reply.

I believe it is running on the latest version of SQL.

Many thanks

Sitz.

Have you solved this yet? Again, I think what you need to do is get someone with more experience to describe what is going on. What you say makes no sense, since adding data to a database most definitely does *not* cause a recompile.
I don't think anyone can help you with the lack of technical information you are writing.

I think I get the idea of what your devs are saying.

Your site navigation, or more correctly, the main links in most of your pages, are dynamically retrieved from your reviews database.

Each time you or anyone else does an update ( either add a review, change content, etc. ) to the db, of course your pages should reflect the updates.

Now that depends on how they link the db to your pages.

I may be guessing wrong here, but I have designed and developed something similar for a client before, and I don't think there is any need to "rebuild" any thing if the source of the content changes, IF the controls on your pages are set to dynamically bind to the db. This way, updates are automatically reflected on the subsequent request to the page.

For example, I have anonline shop that gets 90% of its content from an XML Web Service, wherein constant changes are inevitable ( new offers, new merchants, new categories, pricing, availability, customer reviews, etc. ). But I do not have to "rebuild" anything each time the source of the content of the pages change.

Anyway, they must have a reason that I am not aware of.

HiSitz

I can't open your site.