There has been a flurry of updates released to Microsoft's Silverlight over the past couple of months (Silverlight 2 beta 2 runtime + dev tools, RC0 + dev tools which broke beta 2 apps), and recently Microsoft has released the RTM.
I have been trying (unsuccessfully) to integrate Sharepoint 2007 and Silverlight. Many of the sharepoint/silverlight blogs i have read are outdated, meaning that they target SL Beta 2.
So, my question is...
What steps are necessary in order to host a Silverlight 2.0 (RTM) application, in a web part, on Sharepoint Server 2007 ?
I haven't tried this out but
it seems like a good start:
Silverlight Blueprint for SharePoint
This isn't too difficult to do. There are a few steps you need to follow:
Update IIS with the xap mime type.
Put your files some that SharePoint can get them. In our case we developed a feature which deployed the silverlight javascript files and our xap out to folders in the ISAPI folder (%Program Files%\Common Files\Microsoft Shared\web server extensions\12\ISAPI). We created a folder called _xaps to host these files.
Put the Silverlight object code in either the page itself or in a content web part.
[EDIT: For some reason my object code isn't showing up. So here is a link to an example instead]
That's all there is to it. You're probably best off creating a feature to copy of the files and update whatever page you're hosting the control in. But to just stick silverlight in SharePoint the above should work.
This might help: http://www.u2u.info/Blogs/Karine/Lists/Posts/Post.aspx?ID=40
If you are going to be using User Controls [i.e. Web Parts], then I'd highly recommend looking at SmartPart. You'll still need to do the things in the blogs above to get the assemblies recognized, trusted, etc, but this may help you get your user controls deployed faster.
Related
I've got this scenario: I want to build a website to a friend só he can manager his business. I want to do it like it is going to be online, using C# MVC. The thing is that only my friend will use the system, on localhost:/something...
My question is: if I put the files of my app on Apache, installed in my friends computer, will he be able to access the web site thru localhost:/mysite...?
I think for your use case ASP .net Core makes perfect sense. Have a look at the these articles and sample
https://docs.asp.net/en/latest/intro.html
https://github.com/aspnet/MusicStore
Easy to run/deploy and don't need IIS Install either.
https://sourceforge.net/projects/mod-aspdotnet/
mod_aspdotnet is a loadable Apache 2 module for serving ASP.NET
content using the Microsoft's ASP.NET hosting and .NET runtime within
the Apache HTTP Server process. Non-Windows users should look at mono
(mod_mono) for an alternate implementation.
I am developing an MVC5/EF6 web application hosted on Azure using Visual Studio 2013. I have just got to the portion of development whereby I need to create the reports. I was trying to use Microsoft.ReportViewer to achieve this and although it works perfectly locally it would appear that the WOW (WAWS) on a standard Azure website does not have/allow enough privileges to generate/return a PDF via a stream reader (http://social.msdn.microsoft.com/Forums/windowsazure/en-US/b4a6eb43-0013-435f-9d11-00ee26a8d017/report-viewer-error-on-export-pdf-or-excel-from-azure-web-sites?forum=windowsazurewebsitespreview). The suggestion from Microsoft was to convert the web site to a web role - I am prepared to do this however it seemed like a "no go" for most contributors - also I cant find any tutorials on the matter (I have posted a new question on this).
My question is, what are my options? SSRS is being deprecated so a server call is out, hand cranking a HTML page does not appeal. The closest I have found to a solution breaks the MVC pattern, but should work see here:
Rendering an RDLC report in HTML in ASP.NET MVC
Any help would be greatly appreciated!
Cheers
David
I ended up creating a web role to gain access to GDI+ and elevated WOWs rights, from there I was able to export directly to PDF which is just what I wanted. Not sure why so many other articles condemned this it seems to work perfectly and the cost differentiator does not seem too bad... yes it is more - however, experiments with the extra small VM has proved quite successful.
I looked at forums and some blogs to find out my answer but could not so posting here.
We have MOSS 2007 and a library where we have documents are stored, I would like to run a client utility which runs a day and export all documents imported on that day along with metadata(Column names)
I don't want to install SharePoint server on VHD or on my development environment because I don't think that just for this cause I need to to have Dev SharePoint environment. I don't want to develop this on my development SharePoint environment and give it to my SharePoint team to deploy on server because I feel I should be able to do just on my XP machine.
As SharePoint object model is available, why I cant take missing dll from server and write a small C# utility to export documents to file system? I assume I should be able to do this with SharePoint web service but my question is can I do with SharePoint object model on my XP machine? I don't want to ask my admin to use stsadm to do required work as part of script.
In SharePoint 2007 there is no support for client-side access to the (server) object model. You have to use web services to comply with the requirements you've presented.
Also, it is not possible to take SharePoint DLLs to a client machine without SharePoint installed, and compile—or even run—code with them. It might be possible to achieve compilability, but the process is tedious and makes no sense at all providing it won't ever run on such machine.
You don't need any DLLs from SharePoint 2007 to use web services.
Getting just DLLs be painful for development - you'll be able to compile your code, but to run/debug you still need full installation of SharePoint.
Note that there is special https://sharepoint.stackexchange.com/ dedicated to SharePoint questions.
Can anyone help or direct me to a guide for using Amazon Web Service in Visual Studio 2010? I tried downloading the .Net SDK from the amazon website but it wouldn't let me add the reference to the .dll because it said that it wasn't build for Windows Phone 7.
Thank you
It seems there's no library for WP7 yet. This is because AWS does not allow cross domain requests (although there are some workarounds like this one), and therefore there's not much from the Silverlight world.
Your options here are:
Create a proxy service that talks with AWS through the .NET api. You will need to publish this service when you go live with your app though.
Build your own library based on REST (AWS will stop supporting SOAP next month). You can find the complete documentation of each web service here. Note that this would take much more time and effort, but you could make it open source so other developers can benefit and contribute to it too.
I would like to upload some files on a server Share Point.
My questions are:
1) I started developing my project as a Windows Service but I read several parts of this WebService. It's mandatory that it's be a WebService?
2) I added the references to. Dll take it from my SharePoint Server (as seen in most discussions) but a little read more shares can not be tested if not solely on where you installed SharePoint Server. Right or there are alternative methods to do this? And also, when we deliver the service, can I install the latter on a machine where SharePoint is not installed (it seems a trivial question, but it seems strange not being able to test
but you install it).
You can only reference SharePoint 2007 assemblies from code that is running on the machine where SharePoint is installed (if you were using SharePoint 2010, you could take advantage of the Client Object Model).
Only the part of your solution that is directly interacting with SharePoint has to be created as a web service. You should create a web service with basic methods like UploadFileToLibrary, deploy it to SharePoint machine and then call these methods from the client (it can be an ASP.NET page or desktop application).
As Kit Menke pointed out in a comment below, it is possible that built-in SharePoint web services will be sufficient for you needs and you won't have to create a custom one:
Upload a file to SharePoint through the built-in web services
Copy.CopyIntoItems method