1.0.0 release #794

Closed
opened 2025-08-09 17:17:42 +00:00 by fergalmoran · 0 comments
Owner

Originally created by @dazinator on 4/28/2017

Hi,
I have an asp.net core 1.0.0 compatible library,
I was consuming beta's of Microsoft.AspNetCore.NodeService, version 1.0.0-beta-000021 to be precise.
I have upgraded my solution recently from project.json (vs2015) to csproj (vs2017) and I notice that tests that previous succeeded, now fail:

image

Downgrading to 1.0.0-beta-000020 seems solves this problem - not sure why.
I have created a repro here: https://github.com/dazinator/NetPack/tree/repro-assy-resolve (just open and run the unit test to see what I mean):

@natemcmaster suggested I should upgrade to the RTM version anyway. However I can't see a release of nodeservices for asp.net core 1.0.0 - it seems to jump from the beta's which target 1.0.0 to the RTM which targets 1.1.0 dependencies. If I upgrade to the RTM, I will have to upgrade all consuming applications from 1.0.0 to 1.1.0 - and sadly, at the current time, this is too much work, for which there is not enough time.

So my question is - would you perhaps consider releasing a version of nodeservices that targets asp.net core 1.0.0 dependencies?

Pretty please with a cherry on top.

*Originally created by @dazinator on 4/28/2017* Hi, I have an asp.net core 1.0.0 compatible library, I was consuming beta's of `Microsoft.AspNetCore.NodeService`, version `1.0.0-beta-000021` to be precise. I have upgraded my solution recently from project.json (vs2015) to csproj (vs2017) and I notice that tests that previous succeeded, now fail: ![image](https://cloud.githubusercontent.com/assets/3176632/25543428/719e538e-2c4e-11e7-8326-547e41d81735.png) Downgrading to `1.0.0-beta-000020` seems solves this problem - not sure why. I have created a repro here: https://github.com/dazinator/NetPack/tree/repro-assy-resolve (just open and run the unit test to see what I mean): @natemcmaster suggested I should upgrade to the RTM version anyway. However I can't see a release of `nodeservices` for asp.net core 1.0.0 - it seems to jump from the beta's which target 1.0.0 to the RTM which targets `1.1.0` dependencies. If I upgrade to the RTM, I will have to upgrade all consuming applications from 1.0.0 to 1.1.0 - and sadly, at the current time, this is too much work, for which there is not enough time. So my question is - would you perhaps consider releasing a version of nodeservices that targets asp.net core 1.0.0 dependencies? Pretty please with a cherry on top.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/JavaScriptServices#794
No description provided.