upgrade netstandard, point to 1.6 (according to latest MVC) #1585

New Issue

fergalmoran · 2025-08-09T17:20:46Z

fergalmoran commented

2025-08-09 17:20:46 +00:00

Originally created by @laskoviymishka on 6/2/2016

add missed projects to solution
fix broken build for them
reorgonize solution folders for sample (adjust to physical paths)

Not really sure regards to netstandard version, but i was unable to build and run projects with current version (1.3). After a little research i found that latest mvc pointed to 1.6 already (see https://github.com/aspnet/Mvc/blob/dev/src/Microsoft.AspNetCore.Mvc/project.json#L40), so probable we should point these version also (we have dependency on MVC package in SPAServices). NodeServices could still be pointed to 1.3.

Also add missed sample to solutions, and adjust correct project.json to them. Reorgonize solution structure for sample, so now it same as physicall structure

*Originally created by @laskoviymishka on 6/2/2016* - add missed projects to solution - fix broken build for them - reorgonize solution folders for sample (adjust to physical paths) Not really sure regards to netstandard version, but i was unable to build and run projects with current version (1.3). After a little research i found that latest mvc pointed to 1.6 already (see _https://github.com/aspnet/Mvc/blob/dev/src/Microsoft.AspNetCore.Mvc/project.json#L40_), so probable we should point these version also (we have dependency on MVC package in SPAServices). NodeServices could still be pointed to 1.3. Also add missed sample to solutions, and adjust correct project.json to them. Reorgonize solution structure for sample, so now it same as physicall structure

fergalmoran closed this issue

2025-08-09 17:20:46 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/JavaScriptServices#1585