Iframes, .NET 2, and why I may need a vacation

[Guest]

We're migrating to a new server (I hate lease expirations!), and our Net
Admin set up the new one before leaving for Colorado on Spring Break.

My assignment was to bring the website over. On our website, we use IFrames
to host legacy ASP pages. That feature no longer works on the new system, and
I have noticed that, unlike on the old system, intellisence is now drawing a
squiggle under the IFrame tag on the aspx page. When I hover, it tells me
that the element is not supported under the current schema.

I've painstakingly duplicated everything on the new system, and have set up
IIS exactly the same. The only difference is that the Net Admin installed
..NET v2 on the new one as opposed to 1.4 on the old. Can that be my problem?
Is there something I need to change to support IFrames under the newer
version of .NET?

Everything else is the same. If you guys can't help me out, why I think I
may just need to head for Colorado as well. (Before my boss sends me on a
more permanent one.)

 

[darrel]

My assignment was to bring the website over. On our website, we use

IFrames
to host legacy ASP pages. That feature no longer works on the new system,
and
I have noticed that, unlike on the old system, intellisence is now drawing
a
squiggle under the IFrame tag on the aspx page. When I hover, it tells me
that the element is not supported under the current schema.

Have you tried it anyways?

iFrames are part of HTML. It really shouldn't have anything to do with .net

-Darrel

 

[Guest]

Oh sure. I did try. I'm simply running out of places to look for differences.
Where would you look?

 

[darrel]

Oh sure. I did try. I'm simply running out of places to look for

differences.
Where would you look?

I'm confused. Where would I look for what?

iFrame is just an HTML tag. VS.net might be flagging it, but VS.net often
flags a lot of things incorrectly it seems that I usually just ignore. An
iFrame isn't compiled or anything, so you shouldn't be getting any
compilation errors either. The only thing that would happen is that you'd
get an error in the browser due to malformed HTML perhaps.

-Darrel

 

[Guest]

You obviously aren't as confused as I am. By places to look, I mean for
solutions to the original problem.

Everything on the new site seems to run identically to the old, except for
the page with the IFrame. When I run that page, everything looks fine in
debug until the IFrame tries to execute. Then I get a page cannot be found
error.

I've checked to make that all the folders and files are in the correct
locations. I've checked webconfig to make sure our keys are right. I've been
over IIS thoroughly, making sure that it is configured the same. After doing
all that, I began to suspect the squiggly line under IFrame actually meant
something.

I haven't taken a hammer to it... yet. But I'm running out of places to look
for the problem.

Thanks for your help. I'll proceed as you suggest; assuming that it is not a
problem with IFrame per se.

 

[darrel]

Everything on the new site seems to run identically to the old, except for

the page with the IFrame. When I run that page, everything looks fine in
debug until the IFrame tries to execute. Then I get a page cannot be found
error.

iFrames don't execute. It's just an HTML tag. That error simply sounds like
whatever page the iFrames's SRC attribute is pointing to isn't there. In
your browser, VIEW SOURCE and see what the iFrame is pointing at.

-Darrel

 

[Guest]

Viewing the source on an error page doesn't really help. From the navagation
bar and from within debug, I can see the path it is trying to use. The path
looks valid. I can give another URL, for example Microsoft.com, and it works
fine. So it is something in how it's parsing the path. I'll just keep working
on it.

 

[darrel]

Viewing the source on an error page doesn't really help.

So, the page that has the iFrame doesn't even load? What's the specific
error?

From the navagation
bar and from within debug, I can see the path it is trying to use. The
path
looks valid. I can give another URL, for example Microsoft.com, and it
works
fine. So it is something in how it's parsing the path. I'll just keep
working
on it.

Oh, yep...you've found the error. The path just isn't pointing to the right
place on the server and/or whatever file it's pointing at is no longer
there.

-Darrel

 

[Hans Kesting]

We're migrating to a new server (I hate lease expirations!), and our Net

Admin set up the new one before leaving for Colorado on Spring Break.


I've painstakingly duplicated everything on the new system, and have set up
IIS exactly the same. The only difference is that the Net Admin installed
.NET v2 on the new one as opposed to 1.4 on the old. Can that be my problem?
Is there something I need to change to support IFrames under the newer
version of .NET?

There is not "1.4" version of the .Net framework, just 1.0, 1.1 and now
2.0. If your old site is compiled against 1.1, I don't think it will
work right away under 2.0. It *is* possible to have 1.1 and 2.0 side by
side, so you might try installing 1.1 as well.

Hans Kesting

 

[Guest]

Actually, we did have both. And I know that in the past we had problems with
the newer .NET, but I may have jumped to the wrong conclusion this time. I'm
still puzzled as to why the path is failing in IFrame. We did change our
Inetpub to a d drive for the first time, but I really thought I had
redirected IIS correctly. Maybe it's there. There are just a lot of little
things that can go screwy on a larger web application like this, that also
supports legacy code, when migrated to a new server configuration. And I'm a
little green at that sort of thing.