I'm working with an asp.net application that produces large PDF documents from HTML. The content is perhaps complex (detailed grid type listings, css styled, running to 40+ pages) compared to typical usage. None of the libraries we've tried are performing adequately. Typically a 40 page document is taking upwards of a minute to render on a powerful multi-core machine.
We are able to decouple the generation from the web application and also pre-generate documents in some cases. Still, the frequency with which content changes requires a faster solution.
So, does anyone have experience of a PDF generation component that can output a content heavy 40 page document in seconds rather than minutes? Or are our expectations unrealistic?
NB: I'd rather not "out" the poorly performing components here as we are seeking support from vendors to make improvements. I've reviewed previously questions posted on StackOverflow and none appear to deal with this type or size of document.
I'm using ASP.Net but my question is a little more general than that. I'm interested in reading about strategies to prevent users from fooling with their HTML form values and links in an attempt to update records that don't belong to them.
For instance, if my application dealt with used cars and had links to add/remove inventory, which included as part of the URL the userid, what can I do to intercept attempts to munge the link and put someone else's ID in there? In this limited instance I can always run a check at the server to ensure that userid XYZ actually has rights to car ABC, but I was curious what other strategies are out there to keep the clever at bay.
I have a large string of HTML that I have parsed with a bunch of already formed links in it. I am looking for a quick way to get rid of all of the links to display just the text. Any help or suggestions is appreciated!
I'm hoping this is an easy one...I'm using Microsoft.Office.Interop.Word to convert uploaded word documents into previewable html files. I haven't implemented it fully, but I've played around with it enough that I think I have a plan that will work... My question revolves around
[Code]....
I'm not in love with the idea of opening word and closing it everytime there's an upload (which I hope is a lot of the time) I'd like to make this a shared object that loads at application start. I have 2 questions that go along with this. 1. I imagine that winword could lock up and that would be a problem, right? 2. to save a document I use wordapp.ActiveDocument, this could have an issue as a shared object, right? I think I'm talking myself right out of this...
My printing task is different from other web projects.
I will explain the task clearly.
I have 3 DIV Tags in a web page.
When I click Print All button in the web page, i have to store the contents of 3 DIV tags in rich text format file. Then i perform some codings for modifying the contents of 3 DIV Tags. Similarly i have to store the contents of them in same rich text file (appending to a file after page break) and so on.
At my asp.net project I need display big documents to user. Beacuse document has a lot of text, I need use paging. Every page should have about 5000 symbols. I want split pages by logical tokens such as <br/> nbsp space.
In my project there is many documents and images in my site and i need to convert all files such as .doc,.bmp,.jpg,.txt in a folder to in adobe format(.pdf) and display in a browser as one complete .pdf file The folder may contain images ,word docs and excel docs powerpoint and Pdfs so how this can be done in ASP with vb.net.
I'm building an asp.net mvc application. I have to make posible automatic printing of some documents. I'm wondering where should I save this documents. If I save them to a folder in solution will they be accessible when application is deployed on server? I'm planning on build console application that will be triggered at particular time from windows service and load documents that are saved in that folder and print them one by one.
my requirement is i want to upload word documents and pdf documents into my website with security (i mean encryption) and i want to retrieve documents by giving password the document should visible(or the document should visible for only some people how to do it)
I have a VB.net page that displays lots of data and gridviews. In one of the gridviews, are links to .pdfs that are associated with the data being displayed. As a "close-out" process when the user is done with the page, I need to figure out a way to take those .pdfs that are showing, and merge them into one .pdf. Is this possible in .NET?
Using data posted by a mobile app to my database (via a web api) I will need to create PDF forms with the data filled in as if a user did that. I never did PDF generation, so some "points" that might decide what to use:
-Forms are pretty much a tabular structure. -Some pages are in portrait, while others in landscape. -Some columns have the data printed vertically. -I will need to put images (saved in database, byte arrays) in some fields.
From what I read so far ITextSharp seems to be a popular choice?
I have to open pdf documents from my website. I was thinking of just doing a simple <a href...> to the pdf document. I noticed that in other places on our websites the programmers always do it in the code-behind using the following code : With Response
.ContentType = "application/pdf" .WriteFile(directory and document location) .End() End With.
I'm looking for a way to export a Word document as a PDF. I would like to do this without the use of a "software printer" (such as CutePDF, etc.) and stick to reference assemblies if at all possible. I'm using Microsoft Office Interop Assemblies to generate a Word Document which I save to a temporary directory. So its not necessary for this solution to interact directly with Microsoft Office, unless it needs to.
point me towards any .NET API that will let me iterate the default documents (default.aspx, index.html, etc.) for the web site? I know I can parse web.config, but that doesn't always contain all of the default documents.
I have a need for users to be able to edit word documents from my web page.
Are there any editors, or components, that will allow me to do this?
A bit of background, the user will be able to upload a word document to my site and then view/edit it from there. There will be no requirement for the user to download the document again but ideally I'd like to keep the document as a word doc at my end.
I am embarking on a project that allows a few administators to upload various files and then make them viewable to a subset of the other users that can login to the site. I'm planning on using ASP.NET MVC and was wondering what the best way would be to store the files? Two thoughts came to mind, storing direcly on the server in a folder and storing them in a SQL database.
The first seems like it might be the most logical but how do you prevent an authenticated user from simply typing in the address of a file that they are not permitted to view. My first thought was to setup the folder so that it would be browsed directly via the web.config, but then how does the user view the files they are supposed to view?
Alternatively, I figured if I stored the files in a SQL server, this would prevent the problem just presented but then how does one take, say a PDF file, store it in the database and then render it to a webpage when requested. Secondly, is this efficient to store files in a SQL server?
We have two subdomains for the same site, we would like that depending on the visited subdomain the initial page varies. But in IIS the default document setting is based on the web.config so...We know that we could use the http:/subdomain/page.aspx but its a requirement that we use only http:/subdomain in the links
Desired example: Click in link http:/subdomain1.web.com --> http:/subdomain1.web.com/page1.aspx (our_website/page1.aspx) Click in link http:/subdomain2.web.com --> http:/subdomain2.web.com/page2.aspx (our_website/page2.aspx)
There is an ASP.NET application www.example.com/APP. From within the application several documents - for example office documents DOCX, PDF, etc. - can be opend. They are accessed via some virtual directory as in www.example.com/APP/VIRTUAL/letter.pdf.
Of course, the documents may only be accessed from within the application, after the user has been identified succssfully. Some documents may only be opened by some privileged users. It should be impossible to open letter.pdf by simply entering the above url into a browser
I am thinking about the following...
The name of the virtual directory is kept secret. After the user has successfully logged into the application, some secret is created. The secret contains the user's ID and some time information (valid from / until). Then, if a document is to be referenced from within the application, the url www.example.com/APP/<secret>/letter.pdf is referenced. In IIS the secret is checked. For this, some of my code is called, when serving a request. If successfull, the url is rewritten as www.example.com/APP/VIRTUAL/letter.pdf. I tried several components, such as the IIS URL Rewrite, IHttpModule, IHttpHandler. Unfortunately, I did not yet succeed.
