Chris May

Some pretty cool skins here.

This article shows a project that somewhat automates building of some files from a vbproj. But, it doesn't quite work right, because some of the DLL references are not correct.

After trying to figure out a way to break large apps into smaller ones for more frequent updating, I came across a solution.

The following compiles a simple webapp into 2 DLLs, where one folder "CompileTest" would contain a seperate DLL.

I am sure I have some extra stuff in these lines, but they work for now.

vbc.exe /libpath:C:\TEMP\SingleSignOnWithMultipleASPNETApps\bin /r:C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\System.dll,C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\System.Data.dll,C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\System.drawing.dll,C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\System.Web.dll /imports:system /rootnamespace:www.testdomain.com /target:library /out:C:\TEMP\SingleSignOnWithMultipleASPNETApps\bin\www.testdomain.com.dll C:\TEMP\SingleSignOnWithMultipleASPNETApps\*.vb C:\TEMP\SingleSignOnWithMultipleASPNETApps\CompileTest2\*.vb

vbc.exe /libpath:C:\TEMP\SingleSignOnWithMultipleASPNETApps\bin /r:C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\System.dll,C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\System.Data.dll,C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\System.drawing.dll,C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\System.Web.dll,C:\TEMP\SingleSignOnWithMultipleASPNETApps\bin\www.testdomain.com.dll /imports:system /rootnamespace:www.testdomain.com /target:library /out:C:\TEMP\SingleSignOnWithMultipleASPNETApps\bin\www.testdomain.com.Compiletest.dll C:\TEMP\SingleSignOnWithMultipleASPNETApps\CompileTest\*.vb

I just read a post that you can use the Location tag in a web.config file to allow users to have access to pages other than just the login page. I didn't think this was the case, but I should look into it.

Here is a link to their setup guide.

Here are some tools that "every developer must have." Not sure about that one.

Here is a list of properties available via ADSI scripts, but you have to run it on a 2003 server.

Here is some stuff from ZoneEdit:
The "whois" information is often wrong, and should not be used. Go to a command prompt/console and enter the command:

nslookup -type=NS yourdomainname.com

If the response does not contain all of the correct name servers, then you should contact your registrar and have them fix it. - To check to see whether a particular server is responding, you can add the server name:

nslookup www.yourdomainname.com ns1.zoneedit.com

If the response has a bunch of 'root-servers' that means the server does not know about the domain name and is referring you elsewhere. - To look for a certain record type, like the "MX" record or the "SOA" record, you can use the parameter "-type=MX" or "-type=SOA".

nslookup -type=MX yourdomainname.com

TTT Gallery but Im not sure if it will work with the new version of DNN.

Here is a full SMTP conversation:
telnet 127.0.0.1 25

Trying 127.0.0.1...

Connected to 127.0.0.1.

Escape character is '^]'.

220 extendnet.internal ESMTP

HELO testpc.extendnet.com

250 extendnet.internal

MAIL FROM:scottl@ExtendNet.com

250 ok

RCPT TO:esi@mcn.net

250 ok

DATA

354 go ahead

TO:esi@mcn.net

FROM:scottl@ExtendNet.com

Subject:test

See Subject

.

250 ok 928143441 qp 16779

QUIT

221 extendnet.internal