B
Brett Ryan
Guest
I want a painless way to be able to generate progress OpenClient proxies for .NET.
I find there isn't anything pleasant about the proxy generation process, in fact I almost always punch a screen when I have to use it.
My current problem is it's putting stupid ending comments in the source files which are invalid stating * END COMMENTING OUT DATASET CLASS */. It deletes the files though and just gives the CSC error which you then needs to quickly trap the files before being deleted.
So, does anyone know of a painless way to reliably generate proxies from the command line that does not have hard-coded values for CSC and XSD paths etc.
Better yet, if anyone knows when progress will get off their butt and finally develop a proper SQL driver for .NET I'd love to hear about it, I never want to see the app-server ever again.
Continue reading...
I find there isn't anything pleasant about the proxy generation process, in fact I almost always punch a screen when I have to use it.
My current problem is it's putting stupid ending comments in the source files which are invalid stating * END COMMENTING OUT DATASET CLASS */. It deletes the files though and just gives the CSC error which you then needs to quickly trap the files before being deleted.
So, does anyone know of a painless way to reliably generate proxies from the command line that does not have hard-coded values for CSC and XSD paths etc.
Better yet, if anyone knows when progress will get off their butt and finally develop a proper SQL driver for .NET I'd love to hear about it, I never want to see the app-server ever again.
Continue reading...