Using MS Access desktop and trying to create a new sub-folder in Sharepoint (office 365 version) for each record created. Have scoured the web for ideas, tried MkDir, json, and scripting but cannot figure it out. I am sure it must be fairly simple. It works locally to my computer so the issue is me not understanding how to connect to Sharepoint on the cloud.
Lots of brilliant people out there, any ideas?
Related
I need your help on a generic question. I am using Visual Studio 2012 to develop my Windows Forms Application that is running only on my machine locally to support my work. I have Windows10 and Office2016 installed. My Application interacts with MS Access (via System.Data.OleDb) and Outlook+Excel via Office.InterOp. Fine.
Today I received the information that our Company is rolling out Office365 and I started researching how this could impact my development work. I am not a programmer (more business) but always try to teach myself. But in this case I have no clew what all that means. I read about registering my Application before I connect to Outlook, Outlook REST API and many other things.
So my questions are:
Will my Application work the same way after migrating to Office365 (InterOps) ?
Is there a good tutorial out there that helps me getting started?
I really appreciate any help and guidance on this. Have a great weekend. Thanks
First what is yoy current version of Office you use ? Then do you know if your compagnie will move to office pro plus ? (I suppose yes)
Even if you pass to Office ProPlus the interop will still work, you should after starting to move you app using Graph API, but this API is to interact with the Office 365 data, not the Office App, it's in this case you register your app o the Azure Active Directory to have the right to use Office data
New project in Visual Basic using Visual Studio 2013.
Want to add the "Microsoft Internet Controls" component but I can't find it.
What am I missing?
This is the second link on Google:
http://answers.microsoft.com/en-us/office/forum/office_2010-customize/cant-find-reference-to-microsoft-internet-controls/e138ff0c-8046-47b1-9c0c-ac28cebe3c7a
Apparently it may have been renamed "Microsoft Browser Helpers" and you may need to add a reference to "ieframe.dll".
If you need FTP, it is fully supported in the .NET framework. You could start with the examples on MSDN: https://msdn.microsoft.com/en-us/library/ms229718%28v=vs.110%29.aspx
The inet1 Internet Transfer Control is installed with MS Office. Install it and you should have no problem having it become available to use in Visual Studio etc.
It's old but still completely useful in apps. It did all the FTP and HTTP calls for a web crawler I wrote years ago and was fast and completely error-free when crawling 100s of 1000s of web pages at a time while I slept. I'd use inet1 today if I was writing an app that did huge amounts of internet calls as quickly as possible.
we currently have the need to display Webparts of a Sharepoint 2007 instance in another Portal (Liferay). I'm not familiar with Sharepoint. After some searching, I wasn't able to find a satisfiing answer. For Sharepoint 2007 there was announced the WSRP Toolkit (Webservices For Remote Portlets). http://archive.msdn.microsoft.com/WSRPToolkit
Does anyone know if the Toolkit still works somehow the 2010 Version of Sharepoint (I failed when I tried)
Is there maybe a way to access a single Webpart by URL (-parameters)
Does anyone know another way to solve the Problem of displaying webparts in other Portals?
Thanks for you attention,
Andreas
Does a custom (i.e. one I've developed for SharePoint 2010) visual webpart have to operate within a sandbox solution in SharePoint office 365, or can it be a farm solution?
Thanks, Confused
Web parts have to be sandboxed for SharePoint 365. Visual web parts can't be sandboxed since the ascx control that comes with the web part is copied to the file system. if you need to create a visual web part in SharePoint 365 you can use the SharePoint Power Tools extension.
http://visualstudiogallery.msdn.microsoft.com/8e602a8c-6714-4549-9e95-f3700344b0d9
There you have the option to create a visual web part that can be deployed as a sandboxed solution.
Independent from the type of SP-I (SharePoint Item) you're creating, Office 365 only supports sandboxed solutions.
Microsoft is going to migrate Office 365 to SharePoint 2013 within the next weeks/months. When migration is done, you can also create Apps using the new SharePoint 2013 App model.
But for now, it's only possible to deploy Sandboxed solutions, because it's not allowed to do any changes to the filesystem or elements, that are available across the boundaries of your SiteCollection.
When it comes to WebPart development, you've to remember that it's not possible to impersonate using SPSecurity. (There are more limitations for Sandboxed Solutions, you should revisit the MSDN in order to get a common understanding of what you can do within the Sandbox)
I understand that you can't develop in Visual Studio 2010 for a remote Sharepoint 2010 server because you need a local copy running on your box. (I know there is a hack)
In my situation I have Sharepoint Foundation installed locally for development purposes but I'm not sure how to get the custom lists, etc from the remote server to my local box so I can develop against the same objects.
I've tried exporting the site on the remote box and then creating a new Visual Studio 2010 project from it. This resulted in exceptions when deploying to my local box - more problems which I'm sure given time I could work out...but more problems. (It was types not being installed properly on my local box that the custom object was using)
So I've been thinking there must be an easier way to pull down data structures.
I've spent a while looking for this and while there is quite a lot of information out there I'm finding it hard to find basic information like this.
Any help is greatly appreciated.
What objects do you need from the remote server?
If it is lists, you can export the lists from the remote server as templates then use the resulting stp files to create the lists locally. If it is dlls you can get them form GAC and add the required entries in SharePoint site web.config.
You can also try to export the entire site and create a site locally based on the site template.