sandboxed web parts inside SharePoint 2010 - sharepoint-2010

Is it possible to develop a web-part in ASP.NET (framework > 2.0), to have a sandbox architecture, and deploy those web parts inside Share Point 2010 and/or MOSS 2007
we donot want to use any SharePoint dll reference with web parts we develop.
we refer to the url, section at http://msdn.microsoft.com/en-us/library/ee539417.aspx (section Web Parts in Sandboxed Solutions)

i referred the following How Tos, hope it helps some one ..
http://blah.winsmarts.com/2009-12-SharePoint_2010_Sandboxed_Solutions__The_basics.aspx
_http://www.sharepointdevwiki.com/display/sp2010/SharePoint+Sandboxed+Solutions
_http://www.endusersharepoint.com/EUSP2010/2010/04/05/introduction-to-sharepoint-2010-sandbox-solutions-for-site-collection-owners

I've just hit this problem - looks like it's not meant to be possible which is really annoying.
See: http://msdn.microsoft.com/en-us/library/gg615454.aspx
Specifically:
Application pages, mobile pages, and user controls (.ascx files) cannot be deployed in a sandboxed solution.
However, there is a workaround (hackaround!) here:
http://stefan-stanev-sharepoint-blog.blogspot.com/2010/02/visual-sandbox-web-parts-possible-after.html
I'd love to have a better way!

Related

Javascript in Office

I am trying to understand how to develop add-ins/macros in JS for Office, do I need VSTO for it or does it run from Office somewhere?
I did understood that Microsoft is making the first steps toward replacing VBa with JS and impemented an API to develop macros in Office.Js simmilar to the one Google has for it's Docs. But where can I find a development enviroment for Office.js?
The new web-based add-ins are basically a web application executed in the context of the Office application, either on the Desktop (by embedding a browser, IE11 at the moment) or in the browser (Office Online) where everything is web-based already.
The add-in can be hosted on any web resource you like. You just need to specify a source location URI.
Settings and metadata of the add-in are defined in a manifest file. The article Office Add-ins platform overview describes it very well.
Development can be done in any editor or IDE suitable for coding web apps. There is no Alt+F11 VBA IDE anymore, but you may try the Script Lab add-in, a Microsoft Garage project that allows you to try out some code directly in Office and share code snippets. It includes a great collection of sample code too.
The new WebApplications are hosted on a Webserver. You can develop Office Apps with Visual Studio.
Here is a good course for developing Office Apps including an overview of the Javascript Office API:
https://mva.microsoft.com/en-us/training-courses/introduction-to-office-365-development-8329

Host Vb .Exe on Sharepoint Site

i want to host a vb project from a sharepoint folder instead of having it locally installed.
I am still new at this, but I only need to host the files in the same folder on sharepoint right? And then whoever can just click the .exe file, correct?
Sorry if this is a dumb question!
Thanks in advance
As already mentioned in the comment SharePoint isn't meant to store or even display applications (.exe). What started as a security measure is now part of the philosophy of MS SharePoint. Here's a list of all filetypes SP13 will block by default.
Back to your question. There is a trick how you still can upload an .exe to SharePoint:
Store the application in a folder
Zip the folder
Upload the zipped folder to a document library
Display the library on the desired site
For the future..
As there is a "Silverlight Webpart" - develop silverlight application if you know from the beginning that you want to display them on SharePoint.
Another trick: Publish your application on a host server. Then use the "Site Viewer WebPart" and point it to your application
Last one, although I wouldn't suggest it.. You can develop a .wpf-application and simply upload it as the file-type isn't blocked. But to embed the resources is just a pain in the ass..
There are for sure many other ways to do this.. Those are just the most practical ones I know if you already developed the application. The best solution is of course to create your own WebPart..

Easy way to have a VB.Net WindowsForms application work as a web app?

I have made a small text based game using VB.NET in a Windows Forms application but it seems that people are a bit hesitent when it comes to downloading exe files. What would an easy way to have it work as a web application without having to rewrite the entire code?
There isn't an "easy" way to turn it into a web application. You can take all of your logic and put it into libraries (Class Library), but you'll need to write new front-end code for both the desktop and web.
If you are wanting the web to accept user input and such without constant reloading, you'll also need to make a web service to talk to using jQuery or the like.
For what it's worth, if anyone is hesitant to download an EXE, then they don't need it. I used to publish installations for VB6 applications on my website years ago, and I had downloads and referrals from all over the place, including educational institutions.
Also, if you are direct linking to an EXE, consider packaging it up in a ZIP along with a readme file.

Use Office Interop on ASP.net MVC6 website

I want to generate word documents from my ASP.net MVC 6 website. I've implemented several ways to generate a document in a POC : DocX, NetOffice, OpenXml, COM Interop objects. I was seduced by it.
I made a Console App to test and it works.
But, with ASP.net MVC6, we can't reference Console App's or COM Assemblies.
We need to create "Console App (Package)".
How can I add COM Assemblies to my ASP.net MVC 6 website ?
Microsoft does not currently recommend, and does not support, Automation of Microsoft Office applications from any unattended, non-interactive client application or component (including ASP, ASP.NET, DCOM, and NT Services), because Office may exhibit unstable behavior and/or deadlock when Office is run in this environment.
If you are building a solution that runs in a server-side context, you should try to use components that have been made safe for unattended execution. Or, you should try to find alternatives that allow at least part of the code to run client-side. If you use an Office application from a server-side solution, the application will lack many of the necessary capabilities to run successfully. Additionally, you will be taking risks with the stability of your overall solution.
You can read more about that in the Considerations for server-side Automation of Office article.
Consider using third-party components designed for the server-side execution or if you deal with open XML documents you may use the Open XML SDK, see Welcome to the Open XML SDK 2.5 for Office for more information.

difference between "applications" folder and the "hot-deploy" folders in ofbiz?

I'm new to ofbiz. I create an application in my "ofbiz/hot-deploy" folder. In some site, books they mention our application should be present in "applications" folders also. But I don't know the difference between put user defined applications in the folders namely "hot-deploy" and "applications" in ofbiz.
Please tell the difference, because it will be very useful to my project. Please forgive my mistakes in my questions because I'm new to ofbiz .
Thanks & Regards,
Sivakumar.J
applications is where the OOTB apps provided with the OFBiz framework like marekting, order, party reside. It is best NOT to put your stuff there so you can forward integrate with the next version of Ofbiz.
application components: they are generic applications that can be used as they are or extended/customized (product, order, party, manufacturing, accounting etc…); application components have access to the services and tools provided by the framework components and to the services published by other application components
hot-deploy is where you put your custom application which also has access to the services underlying from the framework.
So if you make a new application say SivakumarWebApp then place it in the hot-deploy, and it can access the framework components as well as other application components.
http://www.hotwaxmedia.com/apache-ofbiz-blog/ofbiz-tutorial-custom-components-in-ofbiz/