Troubleshoot installation problems (Technical Communication Suite on Windows Vista)

What's covered Beginning troubleshooting Intermediate troubleshooting Advanced troubleshooting This document can help you resolve problems that interrupt the installer for Adobe Technical Communication Suite on Windows Vista. These problems can manifest themselves in many different ways, including (but not limited to) a frozen...

[frame_dev] Re: Compiler Selection

— In frame_dev@yahoogroups.com, “elmsoft_frank” wrote:
>
> The FDK for FM8 has been released. Unfortunately the docs are the same
> as for the last beta. They still refer to compiler of choice being
> Visual Studio .NET 2003, even though it appears that the compiler that
> the FDK for FM8 prefers is .NET 2005.

The samples folder now has Visual Studio 2005 .sln and .vcproj files,
so this is another indicator.

> We would prefer to use one compiler, but we build clients for FM 6.0
> through FM 8.0.
>
> Has anyone successfully used Visual Studio .NET 2003 for FM 8?

See the posting from Scott Prentice. This has worked for me on a
simple plugin.

I believe that you must add his code before you #include any headers
from the FDK. This is because the FDE headers redefine the native
types that his code is using. Alternatively, you can use the #define
DONT_REDEFINE directive to prevent this redefinition, and then add
Scott’s code wherever you like.

Also, if FrameMaker and the FDK have been created using Visual Studio
2005, they must have been compiled multi-threaded. The .vcproj files
in the FDK8 samples are also set up this way, giving further evidence
to support this.

I’d therefore suggest that for the 8.0 FDK, you set your projects to
generate multi-threaded code. In the Properties dialog, navigate to
C/C++ > Code Generation, and set the Runtime Library property to
“Multi-threaded (/MT)”. This is the same value that the sample files
are using.

The above is, of course, just a best guess in the absence of any
documentation.

> Also, has anyone used Visual Studio .NET 2005 for clients with the 6.0,
> 7.0, 7.1 and 7.2 FDKs?

For version 7.2 and earlier, the FDK was built single threaded.
Clients should therefore also be built single threaded, with the
Runtime Library property set to “Single-threaded (/ML)”. But Visual
Studio .NET 2005 does not support this option.

So if you do use Visual Studio .NET 2005 to build clients for version
7.2 and earlier, you will be linking the multi-threaded objects that
it builds from your code with the single threaded libraries in the
FDK. This can cause unstable behavior.

Yahoo! Groups Links

To visit your group on the web, go to:
http://groups.yahoo.com/group/frame_dev/

Your email settings:
Individual Email | Traditional

To change settings online go to:
http://groups.yahoo.com/group/frame_dev/join
(Yahoo! ID required)

To change settings via email:
mailto:frame_dev-digest@yahoogroups.com
mailto:frame_dev-fullfeatured@yahoogroups.com

To unsubscribe from this group, send an email to:
frame_dev-unsubscribe@yahoogroups.com

Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/

Software Toolkit assists technical writers. - ThomasNet Industrial News Room (press release)


Software Toolkit assists technical writers.
ThomasNet Industrial News Room (press release), NY - Oct 25, 2007
... in FrameMaker 8, without the need to re-import files for each update. The new release also adds Unicode support for publishing in multiple languages. ...

[frame_dev] Re: Compiler Selection

I have used 7.1 and 7.2 with VS 2005.
Because we had to export docs to MS Word and MS Excel
we implemented things in C++ and C# (for the office stuff).
Everything worked perfect on all machines until I installed the Service
Pack 1 for VS 2005 on my development pc. The MS people seemed to have
changed something on the compilers so that the plug in would not be
recognized by FM. (there is no error or things like that it just
happens nothing). The C++ plug in dll has an other size if it’s
compiled with VS 2005 SP1 and just works on my development machine and
on no other one any more :-( .
So I test things local and then compile the release it on a VPC Image
without SP1 and that works.
I think it has something to with the dual core support introduced with
SP1.

Yahoo! Groups Links

To visit your group on the web, go to:
http://groups.yahoo.com/group/frame_dev/

Your email settings:
Individual Email | Traditional

To change settings online go to:
http://groups.yahoo.com/group/frame_dev/join
(Yahoo! ID required)

To change settings via email:
mailto:frame_dev-digest@yahoogroups.com
mailto:frame_dev-fullfeatured@yahoogroups.com

To unsubscribe from this group, send an email to:
frame_dev-unsubscribe@yahoogroups.com

Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/

[frame_dev] Re: Compiler Selection

I have used Visual Studio 2005 for 7.1 and 7.2
with no problems. Yet.

- Mark

…………

>
> Also, has anyone used Visual Studio .NET 2005 for clients with the
6.0,
> 7.0, 7.1 and 7.2 FDKs?
>
> Thanks
>

Yahoo! Groups Links

To visit your group on the web, go to:
http://groups.yahoo.com/group/frame_dev/

Your email settings:
Individual Email | Traditional

To change settings online go to:
http://groups.yahoo.com/group/frame_dev/join
(Yahoo! ID required)

To change settings via email:
mailto:frame_dev-digest@yahoogroups.com
mailto:frame_dev-fullfeatured@yahoogroups.com

To unsubscribe from this group, send an email to:
frame_dev-unsubscribe@yahoogroups.com

Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/

Re: [frame_dev] Compiler Selection

I haven’t seen any problems yet .. one client has been receiving fairly
heavy use and it seems fine so far. Keeping my fingers crossed.

It sure would be nice to have real documentation from Adobe though. I
figured that the delay in posting the FDK was so they could get the docs
completed .. apparently not. :(

….scott

Frank Elmore wrote:
>
> Scott. Thanks for the info. Yes, I used that technique with the FM8
> beta and it compiled correctly, but it seemed to generate some odd
> behavior during execution. I didn’t have time to investigate
> thoroughly back then. Have you had any problems running the FM8
> clients built with .NET 2003?
>
> Thanks
>
>
> —– Original Message —–
> *From:* Scott Prentice
> *To:* frame_dev@yahoogroups.com
> *Sent:* Tuesday, October 23, 2007 8:08 PM
> *Subject:* Re: [frame_dev] Compiler Selection
>
> I don’t have VS.NET 2005, so haven’t tried that, but I have built FM8
> FDK apps on VS.NET 2003 (using the beta FDK, not the new one). To
> build
> on VS.NET 2003, I’ve added the following to the “main” source file ..
>
> //————————————-
> #include
> #include
>
> int _stat32( const char *path, struct _stat *buffer ) { return
> _stat(path, buffer); }
> int _wstat32( const wchar_t *path, struct _stat *buffer ) { return
> _wstat(path, buffer); }
>
> long _ftol( double );
> long _ftol2_sse( double dblSource ) { return _ftol( dblSource ); }
> //————————————-
>
> Cheers,
>
> …scott
>
> elmsoft_frank wrote:
> >
> > The FDK for FM8 has been released. Unfortunately the docs are
> the same
> > as for the last beta. They still refer to compiler of choice being
> > Visual Studio .NET 2003, even though it appears that the
> compiler that
> > the FDK for FM8 prefers is .NET 2005.
> >
> > We would prefer to use one compiler, but we build clients for FM 6.0
> > through FM 8.0.
> >
> > Has anyone successfully used Visual Studio .NET 2003 for FM 8?
> >
> > Also, has anyone used Visual Studio .NET 2005 for clients with
> the 6.0,
> > 7.0, 7.1 and 7.2 FDKs?
> >
> > Thanks
> >
> >
>
>

Yahoo! Groups Links

To visit your group on the web, go to:
http://groups.yahoo.com/group/frame_dev/

Your email settings:
Individual Email | Traditional

To change settings online go to:
http://groups.yahoo.com/group/frame_dev/join
(Yahoo! ID required)

To change settings via email:
mailto:frame_dev-digest@yahoogroups.com
mailto:frame_dev-fullfeatured@yahoogroups.com

To unsubscribe from this group, send an email to:
frame_dev-unsubscribe@yahoogroups.com

Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/