Be wary, Visual Basic developers: S4 changes DLLs

Go To Last Post
2 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

When I was packaging my latest Visual Basic creation for release, I noticed that mscomctl.ocx now is presumed to live in the ...\Studio4\dll directory instead of where my "real" one lives at ...\WinNT\system32.

Not a biggie, but can sure cause confusion when your totally unrelated product hits the field and you end up with dll fruit salad (mixed apples and oranges).

Lee

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

This will be fixed in the next release and mscomctl.ocx will be moved to where it belong.
I have done some testing and Windows (at least Windows 2000) rediscover the ocx-file in the systemfolder when the one from AVRStudio is uninstalled or deleted. So there should be no danger of some program stopping to function. But it is not a good idea to copy these files around. Shame on us.

Lars K
Atmel