I've already looked onto ATL, but I honestly couldn't find a place to The trick seemed to be to get the wizard set up right to do most of the work for you, then tweak/extend as needed at the source code level afterwards. In terms of references, I just found stuff of the web heres a few (probably random) links from when I was researching it: Maybe there was a problem with it which meant registration failed? It'd be worth looking for errors/debug-output etc when the registration takes place to check this. It is also possible to register it manually using the regsvr32 exe. I don't recall having any problems with registering the control doesnt VS register it for you automatically after building it? AFAIK, that ought to be enough to make it appear in the test container. > It's the best place to buy or sell services for > you, then tweak/extend as needed at the source code level afterwards. > The trick seemed to be to get the wizard set up right to do most of the work for > random) links from when I was researching it: > In terms of references, I just found stuff of the web heres a few (probably > when the registration takes place to check this. > meant registration failed? It'd be worth looking for errors/debug-output etc > enough to make it appear in the test container. > register it for you automatically after building it? AFAIK, that ought to be > I don't recall having any problems with registering the control doesnt VS > If you have any pointers on when to start (web resources, source code,
> everything, it apparently didn't become visible to the Control Test > I've built an ATL project (using the template), and while it compiled and > I've already looked onto ATL, but I honestly couldn't find a place to Though, instead of having it as a VB script: If you look at Build Events/Post-Build Event, it has:Īlso, I found this as a really good tutorial, where in step 7 you can embed it into a webpage: VS should be registering the control for you.
0 kommentar(er)
