I have tested the scenario using Aspose.Pdf for .NET 10.4.0 in Visual Studio Premium 2013 running over Windows 7 (X64) and I am unable to notice any issue. As per my observations, the Intellisense is properly working. However we will further test the scenario by getting NuGet package for Aspose.Pdf for .NET 10.4.0 and will share our findings.
Oh, I just wanted to let you know, when I was evaluating PDF components, I almost passed up Aspose just because it didn’t have any intellisense documentation from the NuGet package. You might want to fix this rather quickly as a lot of devs get their components from NuGet.
I have again tested the scenario in Visual Studio 2013 Premium project with target framework as .NET Framework 4.5 and as per my observations, the intellisense properly works for Aspose.Pdf for .NET 10.4.0 referenced through NuGet package. I am still not certain about the reasons of “why intellisense does not work in your environment”.
If you have any further information/thoughts which can help us in reproducing this issue, then please do share the details. We are sorry for your inconvenience.
I have tested the scenario and I am able to reproduce the same problem that summary description is not being shown for methods and properties. For the sake of correction, I have logged it in our issue tracking system as PDFNEWNET-38831. We will investigate this issue in details and will keep you updated on the status of a correction.
This is still an issue in the latest version of Aspose.PDF .NET. Can you fix this? It’s super hard to code with your API as the methods and classes have no definitions. I have to code by trial and error and the rendering takes time in between. This sucks.
I am afraid the earlier reported issue is not yet resolved. However I have intimated the product team to try accommodating this problem in their development schedule and as soon as we have some further updates, we will let you know. However as as workaround, you may consider using following workaround.
Click Tools -> Options -> Uncheck all checkboxes highlighted in attached image and then re-check all the checkboxes. Click OK button
The earlier shared workaround is a temporary solution and during my testing with Visual Studio 2015 on Windows 10, I am able to use intellisense. However for permanent solution, we request you to please be patient and spare us little time.
As soon as I upgraded to 11.8 (from 11.7) it gave me a build error on using Aspose.Pdf.Text.TextOptions;
CS0138A ‘using namespace’ directive can only be applied to namespaces; ‘TextOptions’ is a type not a namespace. Consider a ‘using static’ directive instead
Although, and sorry to throw another wrench in this, the documentation you have is not helpful. Many of the method summaries I’ve checked pretty much just define the method name with itself.
For instance:
TextFragment
Represents fragment of Pdf text.
TextFragmentCollection
Represents a text fragment collections.
Document
Represents a PDF document.
Document.RemovePdfaCompliance()
Remove pdfa compliance from the document
PdfPageStamp
Constructor of PdfPageStamp
Other documentation is awesome though. I just thought I’d let you know in case you’d like to do a documentation audit.
As soon as I upgraded to 11.8 (from 11.7) it gave me a build error on using Aspose.Pdf.Text.TextOptions;
CS0138A ‘using namespace’ directive can only be applied to namespaces; ‘TextOptions’ is a type not a namespace. Consider a ‘using static’ directive instead
Hi Dirk,
Thanks for contacting support.
There have been some API changes in recent release versions. The major change includes movement of all classes/enumerations from Aspose.Pdf.Text.TextOptions. namespace to Aspose.Pdf.Text. For further details, please visit Aspose.Pdf for .NET 11.8.0 Release Notes
Thanks for the acknowledgement. We are glad to hear that your problem is resolved. Please continue using our API’s and in the event of any further query, please feel free to contact.
dirq:
Although, and sorry to throw another wrench in this, the documentation you have is not helpful. Many of the method summaries I’ve checked pretty much just define the method name with itself.
For instance:
TextFragment
Represents fragment of Pdf text.
TextFragmentCollection
Represents a text fragment collections.
Document
Represents a PDF document.
Document.RemovePdfaCompliance()
Remove pdfa compliance from the document
PdfPageStamp
Constructor of PdfPageStamp
The details and information regarding their usage can be found in Developer Guide of our API.
dirq:
As soon as I upgraded to 11.8 (from 11.7) it gave me a build error on