I'm developing a web application using asp.net 3.5. This application has a lot of documents like .doc, .docx, .rtf, .pdf, .txt, etc... and sometimes the usar need to edit this documents. As a good web application the user need to download the file, edit it and upload again to the server.
I would like to know if is there any way (a component) to make a editor (like MS Word) in webform that allow the user edit the document and save it on server ?
Thanks
You can use the WebDAV protocol to achieve this, which is an extension of the HTTP protocol that allows documents to be downloaded, locked and uploaded and can be kicked off from your Webforms app.
There is quite a mature open source project for .net that you can build upon for your own implementation at http://sourceforge.net/projects/webdav/ with an example webforms project and the code for the server (ignore the comment about there not being source code it's incorrect)
For editing Office docs on a server, there is Office Web Apps. For business scenarios, this requires SharePoint Foundation 2010, which is free with a licensed version of Windows Server.
For non-office documents (PDF), you will need to find another solution for each one, since they are application-specific.
Related
I recently finished a personal web application I had created for my uni. It's mine now to do with as I want. I wrote it on Visual Studio using ASP.Net, CSS, and C#. (I had originally written the first few pages in HTML and PHP, but due to a problem with my computer's inability to run XAMPP, the PHP pages weren't running as required so I redid it on Visual Studio)
The project's initial functionalities (uploading media and documentation, and login and user registration) are there and the pages work, and I plan to proactively work on it to add more features and make it more dynamic and versatile.
However, I have a question, what can I do with it now? Is there a platform (maybe Stackoverflow itself?) that I can upload the project as a whole on to add it to my technical portfolio? or maybe another such action I could do to upload or publish it to add it to my list of things done as a reference for recruiters, or as part of my project history for graduate school?
We have an ASP.NET website that is integrated with a back-end system in a few key places but is largely brochure-ware. The site is localized using resx resources, tied to ASP.NET controls. We would like to hand some of the editing duties to non-developers, but Visual Studio is too intimidating an interface. Expression Web would be perfect, but it does not appear to support localization.
Is there anything else out there that we could try?
UPDATE
To clarify, I am not looking for a resource editor, but rather a web page editor that understands the composition of an ASP.NET web site and its localized web controls, and can present a WYSIWYG editable surface to a non-programmer, while doing the right thing with resource files behind the scenes.
There is SharpDevelop which is an Open Source Visual Studio clone. It works much like Visual Studio, but is much simpler.
It has a built-in RESX editor and basic syntax highlighting. It does not support however navigating from a resource string in an ASPX page to the resource in the RESX file directly.
According to Wikipedia, SharpDevelop allows for plugins, but I do not know of any with such navigation features.
We have some document on the server and want to edit thru asp.net application. So a client can login into his account as related excel file will be hosted on a page of asp.net page.
Does anyone know how to edit server document (excel file) in asp.net from the client side.
If you want to edit the Excel file in your code, in the ASP.NET application, then you may try Aspose.Cells for .NET. This is an API which provides quite flexibility to manipulate Excel files without the need for Microsoft Office to be installed on the server. However, it can only work in the full trust environment, but not a shared hosting environment. Please see if this might help in your scenario. For further details, you may consult the Aspose.Cells for .NET documentation.
Disclosure: I work as developer evangelist at Aspose.
I create a web site via Visual Studio Web Developer. The exension of files are .aspx.
I had also uploaded those files to the hosting server by filezilla client. bt I can't show my pages on the net. Why?
If I write, ../default.aspx, then I meet empty white page include NOTHING.
When I see it on m local computer, there is no any prolem.
Please reply to me as fast as you can.
Best regards, Veli
You will need to "publish" the site using the features in visual studio. This will compile all of your code into the appropriate dll which u will need to upload along with the aspx files
This depends on whether you app is a web site project, or a web application. If it's a web application you'll have to build the site and publish it to your web host. If it's a web site project, you can simply copy the markup and the corresponding code-behinds up.
For more information regarding web deployment of asp.net projects you need to watch the "Web Deployment" section here. It probably will answer many questions you might have regarding this.
Building Applications with ASP.NET 4 WebForms
I'm new to developing in SharePoint and would like some tips please. I want to develop a WebPart. I understand that I effectively need to do this on a machine with SharePoint Server installed and create the web part as an ASP control. Once the control is created, how do I link it into SharePoint?
I would recommend you to take a look at the WSP Builder extensions for Visual Studio. It will simplify the development and deployment process for you, since it contains both templates for web parts, features and it will also package it up in a WSP solution for you.
I would read though this:
http://msdn.microsoft.com/en-us/library/ms452873.aspx
It will answer a lot of your questions about creating a web part, deploying etc.
If you're using the Microsoft Provided WebPart Visual Studio template...it will automatically be deployed to your site when you build it.
If you need to deploy to a test/production environment, you need to create a SharePoint Feature and then deploy the Feature to the server.
http://www.allaboutmoss.com/index.php/2010/03/22/hello-world-sharepoint-webpart-for-beginners/ helps you to create simple webpart and shows how it deploy in server.
You are able to build Web Parts in a number of different ways, through Visual Studio .NET using either the SharePoint Web Part Namespace or the normal ASP.NET Web Part Namespace further you are able to build Web Parts in SharePoint Designer using a combination of different technologies, such as XML Web Services.
XML Web Services will allow you to hook directly into SharePoint using SharePoint's Native Web Services, you can then create a Data View Web Part which will enable you to view, collate, filter and group List Items. This, of course, will also allow you to mingle normal HTML as well as XSLT syntax, allowing you to build logic into the Web Part.
The good thing about doing it this way is there is no "real' coding, i.e. no Code Behind page etc as there would normally be in ASP.NET. This also allows you keep things more or less SharePoint Centric, which is important because you may or may not have access to Central Admin or SSP nor indeed the Server itself, the 12 hive or the GAC.
How you decide to develop Web Parts should include thinking about all of the above, you may have a very restricted development environment. Further, you can also use Namespaces provided directly from GAC assemblies provided by Sharepoint, you may either need access to a development environment which has a MOSS or WSS Server on it or the PIA's or Assemblies from a MOSS/WSS Server.
I am a software developer, however, it is important for me to develop applications which are as SharePoint centric as they can be, which is why I decided to develop my Web Parts in SharePoint Designer. However, there have been times when using full VS.NET is the way to go, I would suggest you look at SharePoint Designer first, get a feel for the interface, XML Web Services, XSLT and HTML once you have created a SharePoint Designer Web Part and Provided this Web Part exists within a Web Part Zone, you can export the Web Part and reimport it into any number of Site Collections.
I must add that the above relates to SharePoint Lists and Libraries but it gives you a grounding to understand how it all fits together. it helped me understand more and made development of more coded Web Parts easier, It may not suit your individual requirements, SharePoint is a huge environment offering many paths.
Hope this Helps you out, search for SharePoint Designer... at least as a starting point.
Cheers