Difference between download version and package version

There are two variants of the installer: Miniconda is Python 2 based and Miniconda3 is Python 3 based. Note that the choice of which Miniconda is installed only affects the root environment. Regardless of which version of Miniconda you install, you can still install both Python 2. The other difference is that the Python 3 version of Miniconda will default to Python 3 when creating new environments and building packages.

So for instance, the behavior of:. If you already have Miniconda or Anaconda installed, and you just want to upgrade, you should not use the installer. Just use conda update. Conda latest. Failing this, yes I suppose you can use bundle-version attribute on the import.

You also need to use the bundle-symbolic-name attribute because otherwise you would be importing from version X of any bundle Frankly I feel it would be better to write a wrapper bundle that depends on the 3rd party framework bundle using Require-Bundle and re-export those packages with a version on them.

That puts all the evil shit into one special place and avoids tainting your "ordinary" bundles with weird attributes on their imports. Show 5 more comments. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Who owns this outage? Building intelligent escalation chains for modern SRE. Podcast Who is building clouds for the independent developer?

Featured on Meta. Now live: A fully responsive profile. Reducing the weight of our footer. Related Hot Network Questions. Question feed. Stack Overflow works best with JavaScript enabled. Accept all cookies Customize settings. Activate Office. Install other apps. Set up mobile devices. Office updates.

Upgrade to the latest version. Troubleshoot and uninstall. I know which version I want. How do I install it? I know I want the bit version. Need more help? Join the discussion. Was this information helpful? Yes No. Thank you! Any more feedback? The more you tell us the more we can help. Can you help us improve?

Resolved my issue. Clear instructions. Easy to follow. No jargon. Pictures helped. Didn't match my screen. Incorrect instructions. Too technical. Not enough information. Not enough pictures. Any additional feedback? Submit feedback.

It uses a third versioning attribute: AssemblyInformationalVersion - the Product version of the assembly. It uses this attribute because nothing else seems to care about it. But this versioning attribute was removed in the AssemblyInfo. When you are in the project of type Analyzer with Code Fix. By default they don't show up but you can discover them from Visual Studio in the project properties Package tab:. In the file explorer properties information tab, Version is shown as "Product version", which is used by NuGet.

Just like the versioning attribute: AssemblyInformationalVersion. So, if you fix a bug or add a new rule, you can change the package version for shipping new package. As to whether it needs to be modified the versions number for Assembly Versions, you can refer to this document for some more details. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams?

Collectives on Stack Overflow. Learn more. Asked 3 years, 8 months ago. Active 2 years, 6 months ago.