![]() ![]() If you really need to just find the file rather than finding the installer from when you initially acquired the component, I'd think you would want to get the copy from the system that's currently being used for development, or (if there isn't a development system set up anymore) a copy that's currently installed wherever the application is being run. I don't know anything about that particular component, but it may also be a violation of the licensing agreement from when your company bought that component. Even if it was a real copy of the component I needed and didn't have malware attached, I wouldn't know if it was actually the same version as what the application had been testing and running with. I certainly wouldn't want to run code on my system that I randomly found on the Internet on a site as sketchy as that one. Well, I'm not sure what you mean by "ok". Is it ok for me to just download a copy off of an external source? It can update the syntax of many things so that it can compile in VB.NET, but that's really all it can do. Well, that's certainly an approach that some people have had success with as a starting point, but don't expect it to solve all your problems with migrating a codebase that you're not familiar with to a new platform. The best option seems to be to use Visual Studio '08 and run the "Upgrade Wizard" when opening the project.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |