Monday, June 18. 2007
TF31002
Unable to connect to this Team Foundation Server...
Microsoft Visual Studio 2005 pops up a nice dialog with three possible reasons for failure:
Well, apparently the appSettings node must be located below the configSections node. If not, all kind of strange things (like not being able to connect to TFS) will occur.
Microsoft Visual Studio 2005 pops up a nice dialog with three possible reasons for failure:
- The Team Foundation Server name, port number or protocol is incorrect.
- The Team Foundation Server is offline.
- Password is expired or incorrect.
Well, apparently the appSettings node must be located below the configSections node. If not, all kind of strange things (like not being able to connect to TFS) will occur.
Wednesday, December 13. 2006
Accessing ASP3.0 Session Object from .NET component
New project, new challenge... How true. A coworker came to me with the following issue:
In an ASP3.0 web application we call a .NET component and we want to access the intrinsic ASP objects (for instance the Session object) from there. Now in a legacy VB COM component you would just reference mtsax.dll, declare a variable as ObjectContext and call GetObjectContext.
Private ObjectContext As MTxAS.ObjectContext
Private Session As ASPTypeLibrary.Session
Set ObjectContext = GetObjectContext()
Set Session = ObjectContext("Session")
After reading a lot about session integration between ASP.NET and ASP3.0 (which I was not looking for), the answer turned out to be extremely simple. Sometimes it is just a matter of looking at the right place. To quote Ohad Israeli, who pointed me in the right direction:
Dim objAppServer As COMSVCSLib.AppServer
Dim objContext As COMSVCSLib.ObjectContext
Dim objSession As ASPTypeLibrary.Session
objAppServer = New COMSVCSLib.AppServer
objContext = objAppServer.GetObjectContext()
objSession = objContext("Session") 'Obtain ASP Session object.
In an ASP3.0 web application we call a .NET component and we want to access the intrinsic ASP objects (for instance the Session object) from there. Now in a legacy VB COM component you would just reference mtsax.dll, declare a variable as ObjectContext and call GetObjectContext.
Private ObjectContext As MTxAS.ObjectContext
Private Session As ASPTypeLibrary.Session
Set ObjectContext = GetObjectContext()
Set Session = ObjectContext("Session")
After reading a lot about session integration between ASP.NET and ASP3.0 (which I was not looking for), the answer turned out to be extremely simple. Sometimes it is just a matter of looking at the right place. To quote Ohad Israeli, who pointed me in the right direction:
The answer is always there…
the problem is that you just don’t look at the right place
Dim objAppServer As COMSVCSLib.AppServer
Dim objContext As COMSVCSLib.ObjectContext
Dim objSession As ASPTypeLibrary.Session
objAppServer = New COMSVCSLib.AppServer
objContext = objAppServer.GetObjectContext()
objSession = objContext("Session") 'Obtain ASP Session object.
