lauraj
- Total activity 26
- Last activity
- Member since
- Following 0 users
- Followed by 0 users
- Votes 0
- Subscriptions 10
Comments
Recent activity by lauraj Sort by recent activity-
I didn't find any alternative; I ended up implementing the "master intro" which is currently rather redundant of the intro to my main assembly. Sigh. Betsy, do please post if you find a workaround.
-
I think this answer is ridiculous. I've got a similar situation, but mine is a mature project to which I've just added a second .NET assembly. The second assembly is genuinely secondary, and I'd li...
-
Yes please!!!!
-
I went ahead and put my Document!X on Vista a couple of weeks ago, and have had no problems till today. Adding a hotspot to an image (.png or .gif) in a content file crashes the Doc!X IDE. I tried ...
-
OK, I solved it by text-editing the .dxp file. Seems a little kludgey, but it works. I just moved the lines identifying the assemblies (near the end of the .dxp) around so they were in the right o...
-
Wow, no answer since 2008? This seems like such a basic thing to want to do. Any updates? I am currently thinking I'll have to remove all my assemblies (which will remove their content files), re-...
-
w00t!
-
I'm still wondering if there's any way to turn off members with [ObsoleteAttribute]. I've tried various ways to do this with the "Include filter/Exclude filter" buttons on the Microsoft .NET Option...
-
OK, I've just found the answer to my second question: On the Filters page, there's a check box for "Exclude members marked with the .NET EditorBrowsable(Never) attribute". Very straightforward, my...
-
I've seen this too. We've sequenced our nightly build to do the doc build before the obfuscation step to avoid the problem.