1. Dale Fuller
  2. SnapObjects
  3. Tuesday, 25 June 2019 19:54 PM UTC

Hi,

Trying to create a simple ASP.Net Core Web API following the steps Bruce laid out in his Demo.  However, after creating the Sample Web API, nearly all of the using directives are invalid.   Example, editing SampleControler.cs,

System, Microsoft, SnapObjects, and PowerBuilder all have the red squiggle line.  Hovering over "using System;" shows the following...

"Unnecessary using directive.  The type or namespace name 'System' could not be found (are you missing a using directive or an assembly reference?)."

So, of course, just about everything else is undefined too.  I can traverse to "C:\Windows\Microsoft.NET\assembly\GAC_MSIL\System\v4.0_4.0.0.0__ " and see "System.dll"

All prerequisite software is loaded.   What am I missing?   Environment variable?  Something in my PATH?  Download something from Nuget?

Environment -

This is an offline installation.

Windows 10

PowerBuilder 2019

SnapDevelop (PB Edition)

 

Dale.

Who is viewing this page
Dale Fuller Accepted Answer Pending Moderation
  1. Thursday, 27 June 2019 16:30 PM UTC
  2. SnapObjects
  3. # 1

Ok. Next roadblock...  Publishing.

I've gone through all the steps. Stared at the documentation for configuring IIS (previously installed).  But continue to get the following when I attempt to publish...

 

"Could not connect to the remote computer ().

On the remote computer, make sure that Web Deploy is

installed and that the required process ("Web Management Service) is started. ..."

 

It is installed and running.  Connection validates in the publish configuration.

What use can I check?

 

Thanks

Comment
  1. Armeen Mazda @Appeon
  2. Friday, 28 June 2019 01:52 AM UTC
Please post separate issues as separate questions so that others with same issue can easily search this Q&A site to find the problem and solution relevant to them. Thanks.
  1. Helpful
  1. Dale Fuller
  2. Friday, 28 June 2019 13:52 PM UTC
Armeen - I hear ya. I went back and forth on that. Will repost.



Logan - That's the documentation I've been "Staring" at. For the release notes...

FTP - nope. Just hitting Publish within SnapDevelop with HTTP destination.

Firewall - Disabled. Tho I cannot attest to what McAfee is doing.

Web Deploy - Web Deployment Agent Service is installed and running. (the reason for the full install)

pfx - Nope. it is signed with a snk file.
  1. Helpful
There are no comments made yet.
Dale Fuller Accepted Answer Pending Moderation
  1. Wednesday, 26 June 2019 19:04 PM UTC
  2. SnapObjects
  3. # 2

Think I just figured it out.  Logged in to my machine with Admin Privileges and granted my normal account modify access to "C:\Program Files (x86)\Microsoft SDKs".  When I re-logged in under my normal account (the one I must use) the squiggles are gone.  

Comment
There are no comments made yet.
Logan Liu @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 26 June 2019 05:49 AM UTC
  2. SnapObjects
  3. # 3

Hi Dale,

When creating a new ASP.NET Core Web API project, I can see SnapDevelop gets 3 packages from Nugets when it's online. Maybe you can add these 3 offline packages to workaround it. 

1) You can get these 3 .nupkg files from Nuget.

https://api.nuget.org/v3-flatcontainer/system.runtime.caching/4.5.0/system.runtime.caching.4.5.0.nupkg
https://api.nuget.org/v3-flatcontainer/system.configuration.configurationmanager/4.5.0/system.configuration.configurationmanager.4.5.0.nupkg
https://api.nuget.org/v3-flatcontainer/system.security.cryptography.protecteddata/4.5.0/system.security.cryptography.protecteddata.4.5.0.nupkg

2) Create a folder, then put .nupkg files into the folder.

3) Then go to SnapDevelop - Tools - Options - NuGet Package Manager - Package Sources.
Click '+' button to add a new package source.
Enter a name. Set the Source to your folder that contains the 3 .nupkg files. Click 'Update' button.

4) Rebuild your project.

Regards,

Logan

Comment
  1. Dale Fuller
  2. Wednesday, 26 June 2019 15:52 PM UTC
Thanks Logan. I'll give it a try. Googling, some suggested doing a "dotnet restore". when I did, it did complain about System.runtime.Caching not being found. So that may be part of the solution anyway.
  1. Helpful
  1. Dale Fuller
  2. Wednesday, 26 June 2019 17:54 PM UTC
Didn't get rid of the squiggly lines. After adding the nupkg files, the rebuild created several "warnings" about "Certificate Chains" and the root cert is not trusted.
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 25 June 2019 20:46 PM UTC
  2. SnapObjects
  3. # 4

Hi Dale;

  Sounds like you might not have installed all the required external SnapDevelop pieces in your PB2019 installation. You might still require items like a MS KB installation,  letting the installer bring down the .Net Core support or also the new Appeon NuGet packages. If you ran the PB2019 install and replied no to these prompts, this could have led you into this situation. If so, uninstall PB (optional) & SnapDevelop and then re-do the PB2019 Install again.

  Just a thought.

HTH

Regards ... Chris

Comment
  1. Dale Fuller
  2. Tuesday, 25 June 2019 21:11 PM UTC
I did re-install SnapDevelop as well as the supporting files in the SetupPrerequisites-2019 folder.

This is an offline installation. Still should have found something as basic as System.
  1. Helpful
  1. Chris Pollach @Appeon
  2. Tuesday, 25 June 2019 21:16 PM UTC
Ahhh .. without an internet connection, the installer might not have been able to download other items for your SnapDevelop environment. It may have assumed that you would do this manually (just my guess).

On my W10 test PC's it did need to download various MS items. However, I had a full unrestricted internet connection.
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.