Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't publish ASP.NET 5 with sapnco_utils.dll reference #31

Closed
skarta opened this issue Dec 26, 2015 · 3 comments
Closed

Can't publish ASP.NET 5 with sapnco_utils.dll reference #31

skarta opened this issue Dec 26, 2015 · 3 comments

Comments

@skarta
Copy link

skarta commented Dec 26, 2015

Hi

After referencing sapnco.dll and sapnco_utils.dll when i attempt to publish my asp.net 5 project I get the following error:

'The package ID 'sapnco_utils' contains invalid characters'...

I understand that this is due to the underscore in one of the the dll names. Any thoughts or suggestions on getting around this much appreciated.

@goenning
Copy link
Owner

I don't think it is a problem with the assembly name.

Where did you get it from? Are they the same architecture as SharpSapRfc.

Do you get this error on compiling or when you're running your App?

On Dec 26, 2015, at 16:07, skarta notifications@github.com wrote:

Hi

After referencing sapncodll and sapnco_utilsdll when i attempt to publish my aspnet 5 project I get the following error:

'The package ID 'sapnco_utils' contains invalid characters'

I understand that this is due to the underscore in one of the the dll names Any thoughts or suggestions on getting around this much appreciated


Reply to this email directly or view it on GitHub.

@skarta
Copy link
Author

skarta commented Dec 26, 2015

They're x86 from the SAP Service market Place. The app builds and runs debugged through visual studio OK, it's only when publishing that this error sadly makes an appearance. I think it's an issue to do with how asp.net 5 projects handle assembly references which has introduced this naming constraint.

@goenning
Copy link
Owner

goenning commented Jan 5, 2016

Well, it seens is is really an issue with naming constraint (dotnet/aspnetcore#874).
Unfortunately I don't know if I can do anything to help you. If you find a solution, please comment it.

Thanks!

@goenning goenning closed this as completed Jan 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants