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

***Note: clean and rebuild solution after consuming...***: Update so… #31

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

tomstonecypher
Copy link

_Note: clean and rebuild solution after consuming..._

Update solution to .Net Framework 4.6; update Nuget packages to latest, except Autofac (version conflict) and UWP (leave at 5.0.0 to avoid reference version warning)

…ution to .Net Framework 4.6; update Nuget packages to latest, except Autofac (version conflict) and UWP (leave at 5.0.0 to avoid reference version warning)
@EricAtMSFT
Copy link
Contributor

Hi Tom,
Thanks for the PR. How did you make this update. Did you just have Visual Studio re-target the .Net Framework?

Thanks

/E

@tomstonecypher
Copy link
Author

Hi, Eric,

Thanks for your email!

It was not an easy process. If I simply let Nuget update everything, I
would get lots of build-time errors and warnings. In the end, I found that
it worked well to:
0. Start with an unchanged repo
1. With Visual Studio, manually reconfigure each of the service
projects to target .Net Framework 4.6
2. With Visual Studio, manage Nuget packages for solution
a. Accept all updates except:
Autofac (version conflicts with dependencies)
UWP - the update would build fine, but generate an ugly
warning about a dependency. I never did get to the bottom of that.

Since the time I generated the pull request, the Autofac issue has been
resolved by some newer versions of its dependencies. So, for my private
build, I have upgraded Autofac successfully.

I've tested all the basic functionality: notifications, DocumentDB, IAP,
etc. However, I have not yet spent time learning the in-solution (service
side and app-side) tests, so didn't run those. Any documentation on how to
run the tests and on the general test methodology, BTW? :-)

This is an impressive and helpful application - thanks to you and the team
for producing this!

/Tom

On Tue, Aug 23, 2016 at 2:04 PM, Eric Langland [email protected]
wrote:

Hi Tom,
Thanks for the PR. How did you make this update. Did you just have Visual
Studio re-target the .Net Framework?

Thanks

/E


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#31 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARWjPNN7jInM7InAgShazCaLbnmJC9R6ks5qizYtgaJpZM4JgscH
.

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

Successfully merging this pull request may close these issues.

2 participants