![]() ![]() Select the Version page and locate the file version including its Build number.In Windows Explorer, locate the component's BPL file. ![]() Version information will be listed on the menu. Right click the control to display the component's popup menu.Place the appropriate component onto a form.Determine its version by checking the value in the 'Version' column.In the Choose Toolbox Items dialog window select the '.NET Framework Components' page.Select the 'Tools | Choose Toolbox Items.' menu item.To Find Out which Version is on Your System If you want to review the What's New document associated with a given release, please review the Version History section below. If instead, I am managing my local copy, I am create more work for myself to maintain the reference and physical copy of dll files.Embarcadero Delphi 11 Alexandria (32-bit)Įmbarcadero Delphi 11 Alexandria (64-bit)Įmbarcadero C++Builder 10 Seattle (32-bit)Įmbarcadero C++Builder 10 Seattle (64-bit)Įmbarcadero C++Builder 10.1 Berlin (32-bit)Įmbarcadero C++Builder 10.1 Berlin (64-bit)Įmbarcadero C++Builder 10.2 Tokyo (32-bit)Įmbarcadero C++Builder 10.2 Tokyo (64-bit)Įmbarcadero C++Builder 10.4 Sydney (32-bit)Įmbarcadero C++Builder 10.4 Sydney (64-bit)Įmbarcadero C++Builder 11 Alexandria (32-bit)Įmbarcadero C++Builder 11 Alexandria (64-bit) So without reference to the Local Copy inside solution, it is pretty much working out of the box whenever I am changing reference, or change between DevExpress versions. On the other hand, because DevExpress will normally automatically add references, and I can using Project converter to update version of DevExpress. My Deployment Project will handle dependency correctly regardless, as far as the reference been setup properly. Without including the dll file, the whole solution wouldn't be able to run inside Visual Studio if the machine don't have the required DevExpress version installed. I would think it is a good idea as it is dependency for my application. But the question is: does it worth the trouble of manage it manually? The way I am going to do is create a SolutionItems directory inside my solution and physically copy all referenced third-party dll files into that folder, then I change reference to that local copy inside the SolutionItems directory. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |