Building Office and SharePoint Apps with "Napa" and Visual Studio
- Posted: Aug 29, 2012 at 8:01 AM
- 34,685 Views
- 2 Comments
Loading User Information from Channel 9
Something went wrong getting user information from Channel 9
Loading User Information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
Right click “Save as…”
In this episode, Jim Nakashima and Saurabh Bhatia show us how to build Office and SharePoint apps using "Napa" Office 365 Development Tools and Visual Studio. If you have an Office 365 account, a browser, and "Napa" you can build apps for Office documents, mail items, and SharePoint. Jim and Saurabh walk us through several examples and then show how to open and deploy Office app projects using Visual Studio.
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums,
or
Contact Us and let us know.
Follow the Discussion
Oops, something didn't work.
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in. You need to be signed in to Channel 9 to use this feature.What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in and view them all on your notifications page.sign up for email notifications?
Great world am interested..
With SPO 2013 and SPD 2013 it appears we have lost some design view development options. It's no longer so easy to create a Custom List forms and Dataview webparts and customize them. And SPO does not offer many options if like me you don't want to work in InfoPath.
I'm playing with NAPA rigth now and wondering about it's limits.. looks very promising. Wondering.. without doing a to of manual coding, is NAPA a good option for building AppPart that can do this.
Build smart and dynamic forms for a SharePoint Custom List (new, edit and display) that the developer has total edit control over. Change behavior of the forms enabling them to bind in other data sources and change the desitination pages on data insert or change? Can this custom AppPart be developed to so that changes to the list are automatically reflected in the developed forms?
Is the above the best approach or should we be calling the stock newform.aspx page into the App somehow?
Remove this comment
Remove this thread
close