You must be logged in to reply to this topic.
Sorry for the elementary nature of this question, but hey, if you don’t know, you don’t know.
When a WinForms application is deployed, does it matter where the C1 dlls are located? Do they need to go into WindowsSystem32 or into the same folder as the exe?
Specifically I am using C1.Win.C1FlexGrid.4.dll and C1.Win.C1List.4.dll.
Hi Jim
Generally when doing this myself I will put any C1 (or other third party dll’s) that I use into the application directory rather than a 'central’ repository on the end users machine. The logic behind this is that your application might for arguements sake be using the latest version of C1 dll’s. Possibly on your end users’ machines there may be one using an app that I or someone else wrote some time ago using an older version of said dlls, so much older in fact that were they to be superceeded by your newere versions of the same that they cause problems with my app.
This should also make it easier for you to update your application as time moves on.
I stress that this is the way that I choose to go, but thus far it has served me well.
Dom
Thanks, Dom, that’s exactly what I needed to know.
You must be logged in to reply to this topic.
As a leading component vendor in the Microsoft Visual Studio Industry Partner program, ComponentOne has been providing the widest range of Microsoft Visual Studio components, IDE platform development tools, and applications for over 22 years. ComponentOne product lines encompass custom WinForms, ASP.NET, WPF, Silverlight, Mobile, and COM components, documentation tools, and Web Parts for Microsoft Office SharePoint Server and Windows SharePoint Services.
Contact ComponentOne: 1.800.858.2739 | Pittsburgh: 412.681.4343
©2013 ComponentOne LLC All Rights Reserved.
All product and company names herein may be trademarks of their respective owners.
ComponentOne holds a license under Patent No. 5,490,216 (which expires on September 21, 2013)
