Command-line interface for Creatio DotNet Core Package

Hello Team,

 

Facing some issues while registering DotNet Core Package on version 7.18. Currently all our development activities were performed in Windows OS and later we would have to package it and deploy in Client OS which is Linux.

 

So the blocker right now is we are getting error while registering our local instance and  it gives 404 error. I understand that the Clio tool is compatible with DotNet Framework so would like to know if there is any other methodology for generating package in DotNet Core. 

 

Appreciate your immediate response. Thank you!

File attachments
Like 0

Like

4 comments

Hello Anupama,

 

I tried replicating the same error message on my side, tried several configurations (including deleting Terrasoft.WebApp reference in IIS, different URLs with the / at the end and port numbers, localhost and actual domain name). I wasn't able to receive the same error:

Are you using the latest clio binary files (they can be found here)? Also can you login to the application from the browser directly? And have I understood you right that you are trying to login to the .NET Core app (localhost:5020)?

Oscar Dylan,

Thanks Oscar for your response. 

 

Yes I am using Dotnet core package and as it is not hosted on IIS and on Kestrel, I am wondering if that is the reason why I am getting 404. To check how the clio command works, I tried hosting dotnet framework package on IIS and the clio command responded successfully.

 

 

Is there any settings that I am missing for the clio to respond for Dotnet Core package.

 

Thanks

Anupama

Anupama,

 

I've also successfully logged into the .NET Core app (but it's hosted on Linux) using clio:

There shouldn't be any specific setting. Can you try re-deploying your local app using .Net Core and hosted on Linux? Also don't you receive any errors in the application logs at the moment of the connect? Logs of the .Net Core app are located in the Logs folder of the root application directory:

Oscar Dylan,

 

It seems to be the Url format which is different for Creatio Dotnet Core and Dotnet Framework package. 

I tried by removing the forward slash from the Url and it did worked and I am able to generate the package. 

Thanks for the suggestion shared earlier in of your messages. 

 

Now we are experiencing another issue. We are running the SonarQube in our project file to do a code quality analysis. So the package includes an Object Code along with the source Code and which is hindering the successful installation of the package. 

Is there any way to ignore that file as I didn't find any ignore command in the github .

 

Show all comments