Beth Massi

@Jon looks like you figured this out via the Visual Studio Team blog

@drcjones  No plugins at all! That is all Visual Studio 2017 version 15.3

@Mario No it's been in VS for a while. Just right-click on the Solution and select "Set Startup Projects" then set "Multiple Startup Projects" 

@Martin - check out the "Using .NET Core 2.0" section of our announcement post: https://blogs.msdn.microsoft.com/dotnet/2017/08/14/announcing-net-core-2-0/

@EricCoffman -- you need to install the .NET Core 2.0 SDK in addition to Visual Studio 15.3. Get it at www.dot.net/core 

Awesome show indeed! Brian, we missed you at the .NET reunion. Good times and way too much cake :)

+1 for interviewing Anisha :)

@annarao - Sounds like you haven't related the document library properly to your database entity. The document library cannot be a top level parent (or unrelated) in this release. It must be related to an entity from your database and be the child part of the relation. (i.e. One Customer has many Documents)

See this FAQ: https://blogs.msdn.com/b/lightswitch/archive/2014/03/20/document-libraries-faq.aspx

Hi Nigel,

What version of Android are you using? The document feature should work with 4.4 or higher I believe.

-Beth

Hi C. Marius,

We just released a new preview this morning that includes client libraries for both .NET as well as JavaScript so you can use this with Universal apps (and a lot more project types in VS). Check out the latest interview for all the details: https://channel9.msdn.com/Blogs/funkyonex/New-Preview-Office-365-API-Tools-for-Visual-Studio

Enjoy!

LightSwitch is still part of Visual Studio and does not require SharePoint. However some features are specific to CBAs & SharePoint (i.e. Document Libraries). Please make sure you check out the latest updates here: https://blogs.msdn.com/b/lightswitch/archive/2014/03/03/office-developer-tools-for-visual-studio-2013-march-2014-update.aspx

Hi Bruce,

Cloud Business Apps ARE SharePoint Apps. So yes, SharePoint is required. However you can deploy to either Office 365 or an on-premises SharePoint 2013 server.

And NO. LightSwitch is still very much part of Visual Studio and does not require SharePoint. We just released a ton of new features for both project types around the HTML client. Please make sure you check out the latest tools here: https://blogs.msdn.com/b/lightswitch/archive/2014/03/03/office-developer-tools-for-visual-studio-2013-march-2014-update.aspx

Hi Jason,

Yes the Silverlight client has some perf issues you should be aware of. If you haven't seen it, check this out: https://blogs.msdn.com/b/rmattsampson/archive/2012/12/28/lightswitch-performance-tweaks-anyone-can-do.aspx

We did optimize what's sent down the wire in VS2013:https://blogs.msdn.com/b/visualstudio/archive/2013/10/09/lightswitch-performance-win-in-visual-studio-2013.aspx

And we also did address a bunch of design-time perf in the March tools update so make sure you have that installed. https://aka.ms/officedevtoolsforvs2013 

Going forward we're seeing customers ask for mobile and better business & data services support so this is why have been working on HTML5 and Office 365. I should mention that the above talk was really well received at BUILD.

Thanks all that came! It was a really fun session.

HTH,
-Beth

Jason, don't shoot yourself in the face, that leaves a messy keyboard.

And to be clear, I only made statements about LightSwitch in that podcast. We have been focusing on HTML client and Office 365 for a couple years now. We will support the Silverlight client as long as Silverlight itself is supported, but our innovation will happen in the HTML & Office365 going forward.

Cheers,
-Beth