Skip to content
sayedihashimi edited this page Sep 25, 2014 · 3 revisions

Meeting notes from 2014.09.03

Attendees

  • @shanselman (msft)
  • @sayedihashimi (msft)
  • @davidfowl (msft)
  • @glennc (msft)
  • @jchannon
  • @nosami
  • @Mpdreamz

Summary

We are at the early stages of seeing ASP.NET vNext development with tools/editors besides Windows & Visual Studio. The first third party tool that we are looking to create an experience for is Sublime Text 3. For the short term we will look at making some targeted changes to OmniSharp/Kulture to get some basic IntelliSense working. Long term we will work with NRefactory guys and come up with a roadmap.

Details

We did a quick round of introductions. Those are below.

  • @shanselman (msft): PM ASP.NET / community owner for Kulture
  • @sayedihashimi (msft): PM ASP.NET Visual Studio / project coordinator for Kulture
  • @davidfowl (msft): MSFT Dev on asp.net runtime / dev contact for Kulture
  • @glennc (msft): MSFT PM on asp.net runtime
  • @jchannon: core dev on Nancy
  • @nosami: OmniSharp creator
  • @Mpdreamz: Contributor on many open source projects

@sayedihashimi is responsible for ensuring that issues are looked after, and will be making whatever fixes that he can. If you have any questions feel free to reach out to him.

One of the questions that came up in today's meeting was "Is Sublime Text 3 the right editor for this"? I've opened issue #26 to discuss this. For now let's keep with Sublime until we make a decision otherwise.

OmniSharp is essentially a wrapper for NRefactory. Some of the features that are provided by OmniSharp/NRefactory.

  • Errors/warnings
  • Code completions
  • Find usage
  • Go to definition
  • Fix usings
  • Running unit tests
  • Showing code docs
  • Refactoring enabling features similar to R#
  • Find implementation

We should reach out to NRefactory guys to discuss futures. We will do that in the upcoming weeks. To get full support for C# 6 that would require NRefactory to build on top of Roslyn which may be a significant effort. For now even though we cannot get 100% accurate IntelliSense we can get pretty close. We should make targeted changes to OmniSharp & Kulture to get some basic support for asp.net vNext enabled. OmniSharp can talk to the Design Time Host to simplify the implementation.

We discussed the idea of having an out of process "c# brain" that would work cross platform. Editors/IDEs would talk to this "c# brain" to get info about the project and perform operations related to code changes.

We should setup a followup meeting for next week.

Next Steps

  • @davidfowl you mentioned that you would create a repo that @nosami could use to get started.
  • [@nosami] Does the DTH work on Mono? If not any ideas what changes would be required?
  • [@nosami] Updates to OmniSharp to enable asp.net vNext
  • [@jchannon] Updates needed to Kulture for OmniSharp integration
  • [@sayedihashimi] Post docs online, create issues for discussion topics and setup follow up meeting

Questions

  • We discussed the idea of designing the "c# brain". Do we have enough info to start designing the interface for communications between the "c# brain" and editors? If not we can add this to the list of topics to discuss in our next sync up.