Gustav Brock
gustav at cactus.dk
Sat Jan 11 07:34:06 CST 2014
Hi Shamil As I understand it, you can use SharePoint of Office 365 meaning zero local install and quite low cost. Among the happy clients of Sharepointinnovations Microsoft Partner Networks is listed. Interesting info as that site has been slow not to say buggy for many years. They will for sure claim that it is caused by the connection to the back-office at MS. Still, I'm not impressed. Thanks for the additional link. /gustav >>> mcp2004 at mail.ru 11-01-14 13:50 >>> Hi Gustav -- Yes, SharePoint could be made a central information portal/business workflow automation engine of many kinds of businesses including e-Commerce, see e.g.* http://www.sharepointinnovations.com/sharepoint-ecommerce/ Yes, SharePoint license costs are prohibitive for SMBs, and the need to install SharePoint locally for development purposes is "blocking" myself from any attempts to make some SharePoint development using Visual Studio, even just to "play" with it. If Excel Services ( http://msdn.microsoft.com/en-us/library/ff640648(v=office.14 ).aspx) or Word Automation Services ( http://msdn.microsoft.com/EN-US/library/ff742315(v=office.14 ).aspx) would become available via APIs like Napa without the need to install SharePoint locally for development purposes and for customers' business usage purposes then it would open an opportunity for a broad range of applications. I have just found this useful article about Napa -* http://www.codemag.com/Article/1211031 *- it looks like you don't need anymore a huge SharePoint server dev PC to develop Office 365 apps from within Visual Studio, well a subset of possible Office 365 and SharePoint apps' types probably, how large is that subset? It would be interesting to know,,, Thank you. -- Shamil Saturday, January 11, 2014 9:44 AM +01:00 from "Gustav Brock" <gustav at cactus.dk>: >Hi Shamil > >I've never heard of Napa but as a "poor man's Visual Studio" even web-based, it seems quite impressive. > >SharePoint has not been in my focus because license costs for local install are prohibitive but - now I think about it - I don't care what drives my app at a remote location as long as the price is fair, reliability is high, and a programming language I understand can be used. > >Thanks so much for the pointer. > >/gustav > >>>> mcp2004 at mail.ru 10-01-14 20:01 >>> > >Hi All -- >Has anybody here tried to *" Sign up for an Office 365 Developer Site" ( http://msdn.microsoft.com/library/office/fp179924 )*and use it in your development? >It looks tempting to try it with " API Tutorial for Office " ( http://msdn.microsoft.com/en-US/office/dn449240 ) and "Napa" Office 365 Development Tools" *( http://office.microsoft.com/en-us/store/napa-office-365-development-tools-WA102963791.aspx?queryid=425f9b37-8494-475c-9e76-74c57dccd8e1&css=napa&CTT=1 ). > > >BTW, "Napa" abbreviation sounds funny here - in Russian, if pronounced: "naa-paaa" (на-па) it could mean "Hey, Dad, watch out, I'll pass you a thing - try to catch it !" :) > >"The thing to pass to Dad" could be a cabbage -* http://en.wikipedia.org/wiki/Napa_cabbage *- is that the word MS used to title their Office 365 Dev Tools? :) I doubt it... > >Then what "Napa" means there? Is that an abbreviation ( http://www.allacronyms.com/NAPA ) or a title/name of something well known? > >Thank you.