If you're working with the IADSLargeInteger to set accountExpires or any other date field in AD, you'll want to know about this bug with the IADsLargeInteger object.
The problem is with the conversion from long to int, if the lowPart is negative, you need to add 1 to the highPart. Otherwise there's a 7 minute, 9.5 second difference with the datetime.
Check here for a detailed explanation:
http://www.rlmueller.net/Integer8Attributes.htm
-pt
Search
Wednesday, September 20, 2006
VS2005 and Web Site App_WebReferences
I've had a problem with VS2005 that's bugged me for a while. I've been working on a web site that uses several web references (web services) and I needed to change where the web reference pointed to create the proxy class for the web site, but I could never figure out where VS2005 was saving the url to the web reference. I changed the web.config, the .disco, the .discomap, and the .wsdl, with no luck. When I would "update" the web reference, they would always revert back to the original URL.
But thankfully, a colleague of mine figured out how get the new URL to work. He updated the .discomap file of the web reference with the new URL, closed Visual Studio, opened it back up, "updated" the web reference, and viola it finally pulled the wsdl from the new URL.
Apparently, VS2005 caches the URL reference to the wsdl, and closing the IDE will clear this cached reference. Thanks Chris!
-pt
But thankfully, a colleague of mine figured out how get the new URL to work. He updated the .discomap file of the web reference with the new URL, closed Visual Studio, opened it back up, "updated" the web reference, and viola it finally pulled the wsdl from the new URL.
Apparently, VS2005 caches the URL reference to the wsdl, and closing the IDE will clear this cached reference. Thanks Chris!
-pt
Subscribe to:
Posts (Atom)