Skip to content
This repository has been archived by the owner on Feb 8, 2022. It is now read-only.

migrate to .NET Core project files #73

Closed
ctaggart opened this issue Dec 17, 2017 · 0 comments · Fixed by #74
Closed

migrate to .NET Core project files #73

ctaggart opened this issue Dec 17, 2017 · 0 comments · Fixed by #74
Assignees
@ctaggart
Milestone
0.5.0

Comments

@ctaggart
Copy link
Owner

I'm going to move the project files over to .NET Core projects. I'll keep the targets the same. We can then discuss what should be .NET Standard.
@ctaggart ctaggart self-assigned this Dec 17, 2017
@ctaggart ctaggart mentioned this issue Dec 17, 2017
Closed
@ctaggart ctaggart added this to the 0.5.0 milestone Dec 17, 2017
ctaggart added a commit that referenced this issue Dec 17, 2017
@ctaggart
migrate to .NET Core project files
73a2c31 
fix #73
@ctaggart ctaggart mentioned this issue Dec 17, 2017
Merged
1 task
ctaggart added a commit that referenced this issue Dec 19, 2017
@ctaggart
migrate to .NET Core project files (#74)
bf84c4a 
* remove Froto.Roslyn

* remove SourceLink v1

* remove more Froto.Roslyn

* migrate to .NET Core project files
fix #73

* image: Visual Studio 2017

* travis ci failing on TypeProvider
created #75

* FAKE 5, stick to net45

* net45 not net452

* try $(MSBuildThisFileDirectory)

* don't test TypeProvider on mono

* just FAKE
@ctaggart ctaggart mentioned this issue Dec 19, 2017
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@ctaggart ctaggart

Labels
None yet
Projects
None yet
Milestone
0.5.0
Development

Successfully merging a pull request may close this issue.

migrate to .NET Core project files ctaggart/froto
1 participant
@ctaggart