Thanks for your request. We are working on this problem right at the moment. Your request has been linked to the appropriate issue. It will be resolved before the next hotfix, which comes out in 3-4 weeks.
in September, Aspose confirmed the fix would be available before the next hotfix which was due out in 3-4 weeks, meaning it should have been released now.
This is a CRITICAL issue for our release.
Can you please provide an confirm release date for the issue, it is impacting our production platform.
Thanks for your request. Release date was moved. The issue is scheduled to be fixed in the next version (10.0.0). We will let you know once it is resolved.
You should note that all estimates we give in the forum are rough estimates. So you cannot 100% rely on these estimates.
Thanks for your inquiry. The best estimate I can give you at the moment is December 2010 – January 2011. We will let you know once the issue is resolved.
But you should note that all estimates we give in the forum are rough estimates. So you cannot 100% rely on these estimates.
In the absence of a fix right now what can we do to ‘work around’ this defect? I need a document that does not appear to be virus infected when openned in Word 2010.
Thanks for your inquiry. As far I know such problem occurs only with DOC format. So as a temporary workaround, you can try using DOCX, WML or RTF format instead of DOC.
Any update on the v10 release that fixes the word 2010 protected view problem? Earlier in this thread dec 2010 / jan 2011 was listed. It is now February.
Thanks for your request. Unfortunately, the issue is still unresolved. We will keep you informed regarding status of this issue and immediately let you know once it is resolved.
You can try this way - view document in the MS Word application within the session.
In addition, your code is shown in the example indicates that you are using an older version of our product. We strongly recommend that you use a new version of Aspose.Words you can download it here: https://releases.aspose.com/words/net/
Then the code I suggest you to use will look like this:
Thanks for your request. Yes, unfortunately, you are right, the fix of this issue is not ready yet. Currently it is scheduled to be fixed before the end of September.
Please note, that all estimate we provide in the forum are rough estimates and you cannot 100% rely on them.
Sets consent for sending user data to Google for online advertising purposes.
Sets consent for personalized advertising.
Cookie Notice
To provide you with the best experience, we use cookies for personalization, analytics, and ads. By using our site, you agree to our cookie policy.
More info
Enables storage, such as cookies, related to analytics.
Enables storage, such as cookies, related to advertising.
Sets consent for sending user data to Google for online advertising purposes.
Sets consent for personalized advertising.
Cookie Notice
To provide you with the best experience, we use cookies for personalization, analytics, and ads. By using our site, you agree to our cookie policy.
More info
Enables storage, such as cookies, related to analytics.
Enables storage, such as cookies, related to advertising.
Sets consent for sending user data to Google for online advertising purposes.