Hi!
My developer machine crashed recently and I need to re-install infragistics. However, I don't want to upgrade infragistics because then I would constantly have different project files because the references would be to a different version than what's under source control. If I checkin my changes to the project files I force everyone on the team to upgrade (true, using exe.conf files I could maybe assembly redirection but I'd prefer not to). So I need to install 12.1.20121.2024 of Infragistics Windows Forms DLLs. I've searched the website and download archives but cannot find the appropriate combination of releases and service releases to produce the right version of the DLLs. Here the reference in my csproj file:
<Reference Include="Infragistics4.Win.v12.1, Version=12.1.20121.2024, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb, processorArchitecture=MSIL" />
I've installed NetSdvantagefor .NET for 2012v1 which takes me to 12.1.20121.1001. If I apply the service patch it brings me to build 2135. I've examined the engineering blog and found that the release I want lies somewhere between these dates:
5-7-2012: release 12.1.20121.1001
http://es.infragistics.com/community/blogs/engineering/archive/2012/05/07/netadvantage-for-windows-forms-release-notes-june-12-1-volume-release.aspx
12-20-2012: release 12.1.20121.2082
http://es.infragistics.com/community/blogs/engineering/archive/2012/12/20/netadvantage-for-windows-forms-release-notes-december-11-2-12-1-12-2-service-releases.aspx
Where can I find or by combination install build 2024? Or, perhaps, you have an alternative suggestion?
Thanks!
Craig
Set "Specific Version" to False on all Infragistic libraries' references, and everyone could work with different builds of the same version of controls.
I am always using the latest build to see if something is fixed or has performance improvements, while the build is made with an older Infragistics build.
HTH,
Emanuel
First, thank you Emanuel.
While that is a solution and one I'll possibly use, I'd rather actually install the same version that other developers, testers, the nightly build machine and eventually customers are using. I want to make sure my development environment matches what's downstream from me.
So I'd rather find out how I can install version 12.1.20121.2024.
Actually, I am curious about your philosophy of trying out the latest.
Have you ever been bitten this choice? That is, have you had a particularly nasty bug because of this or an inability to recreate a customer issue?
Anyway, I'd still like to find 2024. I'm also performing an upgrade to VS 2012 and don't want to have too many moving parts.
C
I have never been bitten by my choice of programming against the latest build because I have a backup development machine set up with the version my users are using. But I hardly touch that machine.
I have found and submitted some bugs, especially regarding to using Infragistics controls with Smart Client Software Factory from Pattern & Practices Microsoft team, so I am using the latest builds to see if the bugs we're fixed and it's ok to deploy those build to our clients.
Hello,
As it was mentioned in the post above changing the “Specific Version” to False in the Infragistics references’ properties menu should help and you also should delete all Infragistics entries from licenses.licx file and save it, then clean and rebuild your solution.
If you need specific build for Infragistics 12.1, please let me know to create support ticket for you in our system, in order to see what we could do for you.
I am waiting for your response.
I think I'll probably need a 12.1.20121.2024 build installed on my machine just so I can replicate what's on the build machine and used by our customer base.
If I don't have 2024, I'll need to set specificversion to false in my csproj file and could be accidentally checked in or at least would be exceedingly annoying because I would have to remove and restore that setting every time I had a legitimate change to the csproj that I needed to checkin.
So, if it is not a big deal, yes, I would like aforementioned build.
Hello Craig,
I have created support ticket for you in our issue tracking system with ID : CAS-124451-V8J2Q1. I will help you with this matter through the mentioned case.
Thank you for using Infragistics components.
After looking into this, your idea “making old versions of the product available for download” has been determined to be a new product idea. You can suggest new product ideas for future versions (or vote for existing ones) at <http://ideas.infragistics.com>.
There are many benefits to submitting a product idea:
- Direct communication with our product management team regarding your product idea.
- Notifications whenever new information regarding your idea becomes available.
- Ability to vote on your favorite product ideas to let us know which ones are the most important to you. You will have ten votes for this and can change which ideas you are voting for at any time.
- Allow you to shape the future of our products by requesting new controls and products altogether.
- You and other developers can discuss existing product ideas with members of our Product Management team.
Steps to create your idea:
The Product Idea site puts you in the driver’s seat and allows you to track the progress of your ideas at any time, see how many votes it got, read comments from other developers in the community, and see if someone from the product team has additional questions for you.
Thank you for contacting Infragistics.
Great job Dimitar.
Could Infragitics making old versions of the product generally available? I'm sure there are other developers who are using a specific version of infragistics and would like to stick with that version until they, as a tema, upgrade. SpecificVersion=false I don't see as a good solution across an entire development team as potentially each developer would be using a slightly different version of the library. If they want to do that they can, but they should not be forced to do that IMHO.
csproj files store the version number of the DLL for references. If someone is not using the agreed upon DLLs they can't checkin their project files without limiting their changes to outside the scope of the infragistics references.
Anyway, just an idea. Thanks again for your great help!