#Programmer and other tech-savvy friends: I'm blanking. I have a .NET EXE that throws a run-time error that suggests it requires an old version of MS Access to run.
I don't need the program to run as much as I need to see what the program would visually look like (what buttons you're presented with, etc.).
In the past I think I did this using dotPeek by JetBrains, but I'm not seeing any such option there now. Ideas?
dotPeek would allow you to reverse engineer the app, the next step would be to identify where in the code it’s actually trying to load Access and removing that part, then you should be able to run it, with the caveat that anything that actually uses the Access API under the hood would obviously be broken.
I guess I'm thinking of how with older VB6 applications you could decompile it and view the .frm which would give you a view of what the application was supposed to look like when run.
That is, realistically, all I really need out of this little endeavor.
Add comment