.Net 2.0 and bin directory

Hi,

I have managed to get aspx simple pages to work within TS (just a HTML page renamed to *.aspx).

Now it is a bit more complicated stuff with code behind files/dll's that we wish to be able to get working in TS.

Has anyone succesfully got the above to work, without separetly having to register the dll's in the GAC ? As each workarea + STAGING will be setup as applications, I think it should be possible to tweak TS, so that dll's in the bin directory are registered automatically.

Platform information: TS 6.5. Windows 2003 server and IIS 6.0.

Any hints/help will be greatly appreciated :-)

Regards
Vaqas

Find more posts tagged with

Comments

Gregg Faus

Since 2.0, I have had more difficulty getting configured correctly as well. To virtualize pages correctly in my environment I had to do the following:
1) Create application space on the document root of the website (e.g. workarea, staging). This is the same as in a 1.1 framework.
2) All SSI references need a ~ in front of the path (e.g. "~/include/header.aspx").
3) All assemblies placed in /bin/ folder. Nothing different here.

Templating is a whole different issue as I have my templatedata directory outside of the document root.

This is on a win2k box. My new win23k box seems to like 2.0 better.

vahu

Hi,

I got things to work more or less. The assembly references are working fine now. But I have run into a new problem/issue with Server.Mappath().

https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=49749 according to the article I created the iwmountdummy directory and etc.. Now when I try to make a server.Mappath("/website/xml/somexmlfile.xml) I get a server error: "Could not find a part of the path 'D:\Inetpub\iwmountdummy\website\xml\somexmlfile.xml". Obviously that physical directory is empty and thereby do not contain the xml file. Why are references being translated like that and not as root of application (the workarea).

Regards
Vaqas

Gregg Faus

I've got the same issue. I haven't spent anymore time figuring it out yet. I had to add the full mount path to make it resolve correctly (e.g. /iw-mount/default/main/etc....).

vahu

Hi Gfaus,

I manage to get the server.mappath() to work. Basically it is the same issue as the assemply refenerce. A ~ in front of the path makes all the wonders.

So my conclusion of .Net and TeamSite is that one should have ~ in front of all kinds of path refenreces in the code, and if one obliges to this, one might be lucky enough that everything will work :-).

Regards
Vaqas