Nuget packages have wrong versions --- breaking SF control builds --

[Megatron]

See below - it shows one version and installs another version with wrong version numbers, the meta data assembly has the wrong numbers

____________________

[Kannan]

Hi Megatron, 

Thanks for contacting Syncfusion support. 

Syncfusion does not publish the Syncfusion.Compression.Base with the v16.3450.0.29. Also, the screenshot itself showing the package not available in this source.  We don’t have this version in any of the Syncfusion NuGet package dependency. While installing the unavailable dependency NuGet package, then it will get installation failed and reverted. This is the NuGet installation behavior. Could you please share the Syncfusion NuGet package name which you are trying to install and installing the Syncfusion.Compression.Base with v16.3450.0.29? 

Regards, 

Kannan 

[Megatron]

Hi Kannan, I am sorry but your answer does not resolve or even address the issue!!

The pictures I have attached clearly show what Nuget has for version numbers. I also fully understand these version numbers dont make sense, therefore I attached the pictures to show/report this problem.

Your response has no inclination to troubleshooting why this is happening. Did you even look at the nuget feeds on your side, I saw this on two different machines.

Can you tell me how to resolve this, removing re-adding has not helped.

The Syncfusion Nuget Path you asked for is below

http://nuget.syncfusion.com/nuget_aspnetmvc/nuget/getsyncfusionpackages/aspnetmvc

If believe there is a more current path please list it below

thanks

[Kannan]

Hi Megatron, 

We have created a new incident for this query please follow up that incident for further details.  

https://www.syncfusion.com/support/directtrac/incidents  

Regards,  

Kannan 

[seo]

Thank you very much for the knowledge. It is very useful for me. I will take it to develop my own knowledge. :)[URL="https://bet007.casino/"]UFABET[/URL] :J

[Active Directory Export Tool]

Awesome post! Really enjoyed this post. Thanks for sharing here.

Export groups from active directory

[Mr James]

We have created a new incident for this query please follow up that incident for further details.  

https://www.syncfusion.com/support/directtrac/incidents  

Regards,  

Kannan 

[Boothcool Apk]

NuGet packages sometimes have wrong versions, and this can cause problems in SF control builds. When the versions do not match, the build may fail or stop working correctly. Developers need to check and fix package versions to avoid errors. APK download site is also used by some users to get apps easily, but it is important to always use safe and correct sources.

[EdbergVasan DallasVaz]

Hi Boothcool Apk,

Thank you for reporting the issue with mismatched NuGet package versions affecting Syncfusion control builds. To help us reproduce and investigate the problem effectively, could you please provide the following details:

• In Which NuGet package and control did you facing issue?
• Please specify the Syncfusion controls and versions you are using?
• Steps followed during build or restore that led to the error
• Any error messages or logs observed during the failure, share the log with us.

Regards,

Edberg Vasan

Why are NuGet packages showing one version but installing a different version with incorrect metadata assembly numbers, causing SF control build failures?

[Suvetha Venkatesan]

Hello,

Thank you for reaching out to us. We understand that you're experiencing an issue regarding installation of mismatched NuGet package versions (leading to SF control build failures), could you please share the following details:

• Name of the exact NuGet package and version you tried to install.
• Name of the package installed: The package name and version that ended up being installed.
• Please specify the Syncfusion controls and versions you are using.
• Kindly share the Screenshots or logs showing the mismatch and the build failure details.
• Kindly attach a screenshot of the package manager console or Visual Studio NuGet window showing the discrepancy.

Regards,
SuvethaVenkatesan