1. Home
  2. Forum
  3. ASP.NET Core
  4. ASP.NET Core Dependcy Notification

ASP.NET Core Dependcy Notification

I am working on a new ASP.NET Core 2.0 web project using Visual Studio 2017 (15.5.2) which has bower deprecated. So I have added Syncfusion ASP.NET Core (15.4.20)  control as recommended by Syncfusion support site using NuGet method.  Everything does seem to work but I noticed that the Dependencies node had a yellow triangle notification. After further inspection I realized that the jquery and jquery-validation nodes had same yellow triangles and were displaying "not installed" but they were installed in the "wwwroot/lib" folder. Can someone tell me if this is really an issue before I push to production in the future. I have included a screen shot for you to look at.

Orgbrat

Attachment: SyncfusionDependciesNotification_95bd3582.zip

3 Replies
PK Prem Kumar Madhan Raj Syncfusion Team January 2, 2018 01:25 PM UTC

Hi Steve,  

Thanks for contacting Syncfusion support.  

We could not able to reproduce the reported issue from our end when installing the Syncfusion Bower packages in the ASP.NET Core 2.0 application.  Please refer the below screenshot for the reference.  
   
  
Based on your screenshot in your previous update, we suspect that notified like “not installed” in the dependent packages since the .bower.json file is not available in the wwwroot/lib/<dependent packages> folder location.  Please refer the above screenshot for the jQuery folder structure after installed the Bower packages in the ASP.NET Core application. To resolve this issue, please follow the below steps.   


 
  1. Uninstall Syncfusion bower packages from your application.
  2. Then, remove the dependencies bower packages from the “wwwrooot/lib” folder location.
  3. Now, reinstall the latest Syncfusion Bower packages and check the dependencies node.

Note: Don’t remove the .bower.json file from the lib folder location since the status of the bower packages whether installed or not in the dependencies node based on this .bower.json file.  

If still the issue occurred, please update the below details to reproduce the reported issue from our end.   


 
  1. Reproducing steps.
  2. Sample application which you have faced the issue if possible.

Regards,  
Prem Kumar. M

SG Steve Graddy January 2, 2018 07:08 PM UTC

Hi Prem,

         Before I try your recommendation, I wanted to let you know that there is no .bower.json file in the lib folder location. There is a bower.json file at the root of the ASP.NET Core project with the following contents...

{
  "name": "asp.net",
  "private": true,
  "dependencies": {
    "syncfusion-javascript": "15.4.20"
  }

Steve



PK Prem Kumar Madhan Raj Syncfusion Team January 3, 2018 12:54 PM UTC

 
Thanks for the update. 
 
Please check whether you have added bower manually in your application since it been deprecated in your visual studio version (15.5.2) as shown in the below link (under exploring client-side build process). 
 
 
If so, then the cause for the issue may be packages might not have installed properly due to some network problem. So, we suggest you to uninstall the previously installed bower packages and delete the dependency packages from “wwwrooot/lib” location and again reinstall the bower packages and then restart your application once to get rid of this issue from your end. 
 
Regards, 
 
Prem Kumar. M

Loader.
Up arrow icon