Could not find type'*Activities'

Help
21

3
3910×602 16.5 KB

22

That is correct, do you see any packages when you click on Official feed on the left ?

23

“No package founf”

24

found*

25

I think the problem is that when you opened the project in the new version of Studio, some old activities that @andrzej.kniola mentioned, did not migrate on the new version.

I also think the problem is because you do not see any packages on the official feed (Studio would have downloaded the new packages from there and migrated the old ones)

1 Like
26

We just need to figure out why.

27

Do you have firewall or proxy enabled ?

28

1
1948×650 47 KB

29

i tried do deactivate firewall. same thing…i didn’t found activities

30

This is a tough one, I never encountered this case when you could not see anything on the Official feed.
You do have internet connection on that machine, right ?

What happens when you open the link below in a browser on the machine where studio is installed ?

https://www.myget.org/F/workflow/FindPackagesById()?id='Microsoft.Activities.Extensions'

This tries to look for a certain package on the official feed
Does it look like this ?

image
image1470×447 66.9 KB

31

1
11909×346 78.3 KB

this it what i see

32

Reviewing the images you sent so far, I saw that you are using a proxy :

image
image820×545 91.2 KB

This means that the nuget explorer from your machine (Studio > package manager) is unable to get passed this proxy.

I found some documentation online on how to set your nuget.config from %appdata%\nuget folder:

Can you please try that ?

1 Like
33

work
work949×564 49.9 KB

Hello, The problem was weird, but the solution was simple.
With help and documentation, both from this topic,
I connected via hotspot to an external network and then I found the missing activities.
You were right. due to proxy settings, somehow I was limited to find those packages

Now it works perfectly.

Best regards,
Hogas Sergiu

34

Phew, glad that worked, I was running out of ideas.
Normally, setting a proxy in network options or in internet explorer means that Studio and package manager automatically benefits from that proxy.
But in your case, the script proxy that you were using was not applied to our package manager nuget tool, you had to do that manually.

Let us know if the project you had, migrated successfully now, and runs without problems.
Your current version might be broken beyond repair, and the fact that you added all those packages to it might lead to future problems.
If it is broken, simply take a packed version done with 18.1, rename it to .zip extension, extract it and take the xaml(s) and project json from there. And migrate it again (open it in 18.4 Studio) with the newly access to Official feed(s).

35

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.