Asp.net with javascript page refresh

ajaxasp.net

I have an ASP.Net appl composed by three pages; page1, page2 and page3
The execution starts on page one. Page1 calls Page2, but page1 has to be visible still, so user can still work on that page. When Page2 closes, a java script function calls Page3, so all the cleaning is done on page 3. When page 3 completes its task, the window goes, and only Page1 is displayed
To call page3 from page two I use something like this;

xHRObject.open("GET", "Default3.aspx?SiEditor=E&idSec=N&F="+idenValue, false);

The problem is the following:
the info updated on page 2, has to be updated on page1, but it does not. If I place I similar java script on page3 to call page1, it instantiates a new page, rather than refreshing the current one. How do I access page1? If we use modal forms for page2, the control goes back to page1 with no problems, but I can not use modals in this case

Any idea how to refresh page1 when page2 and 3 are disposed?

Best Answer

When you create new windows you can access the window that opened them via the opener property. You can then use the location object to reload the page.

So this could be the body tag on your page 2:

<body onunload="window.opener.location.reload([true])">

Website:

The Web Site project is compiled on the fly. You end up with a lot more DLL files, which can be a pain. It also gives problems when you have pages or controls in one directory that need to reference pages and controls in another directory since the other directory may not be compiled into the code yet. Another problem can be in publishing.

If Visual Studio isn't told to re-use the same names constantly, it will come up with new names for the DLL files generated by pages all the time. That can lead to having several close copies of DLL files containing the same class name, which will generate plenty of errors. The Web Site project was introduced with Visual Studio 2005, but it has turned out not to be popular.

Web Application:

The Web Application Project was created as an add-in and now exists as part of SP 1 for Visual Studio 2005. The main differences are the Web Application Project was designed to work similarly to the Web projects that shipped with Visual Studio 2003. It will compile the application into a single DLL file at build time. To update the project, it must be recompiled and the DLL file published for changes to occur.

Another nice feature of the Web Application project is it's much easier to exclude files from the project view. In the Web Site project, each file that you exclude is renamed with an excluded keyword in the filename. In the Web Application Project, the project just keeps track of which files to include/exclude from the project view without renaming them, making things much tidier.

Reference

The article ASP.NET 2.0 - Web Site vs Web Application project also gives reasons on why to use one and not the other. Here is an excerpt of it:

You need to migrate large Visual Studio .NET 2003 applications to VS 2005? use the Web Application project.

You want to open and edit any directory as a Web project without creating a project file? use Web Site project.

You need to add pre-build and post-build steps during compilation? use Web Application project.

You need to build a Web application using multiple Web projects? use the Web Application project.

You want to generate one assembly for each page? use the Web Site project.

You prefer dynamic compilation and working on pages without building entire site on each page view? use Web Site project.

You prefer single-page code model to code-behind model? use Web Site project.

Web Application Projects versus Web Site Projects (MSDN) explains the differences between the web site and web application projects. Also, it discusses the configuration to be made in Visual Studio.

R – ASP.NET Page calls an additional aspx page after loading

Thanks for the tip Andrew.

We figured out what was going on... Page1.aspx in the application is really Default.aspx. On Page2.aspx, another developer put a img tag on the page that did not have src property defined. So when Page2.aspx executed, it was looking for an image located at the web site's root level, this then triggered the code on Default.aspx (Page1) and wipe away the session.

Overall it looked something like this...

On Page2.aspx

<img src=""> <!-- this ended up triggering a call to Default.aspx, wiping the session -->

Hopefully that helps out someone else.

Best Answer

Related Solutions

.net – ASP.NET Web Site or ASP.NET Web Application

Website:

Web Application:

R – ASP.NET Page calls an additional aspx page after loading

Related Topic