LaTeX.org

More information.. The computers that are having this problem had apparently had TexnicCenter installed before. Another Tex editor was installed which took the file associations. If TexnicCenter is installed again, it will not 're-take' the association, even if all other programs using the ...

I find that installing TeXnicCenter in Windows 7 will fail to correctly associate .TEX or .TCP files with TexnicCenter. Other tex editors have options to restore or edit the associations used by that editor.

Does TexnicCenter have a way of restoring file associations with itself?

Is there a ...

There is another way to deal with the executable names and the different search strings. Windows batch files can be used as an intermediary.
I believe this solves all problems except two. The profiles' command-line arguments can no longer be customized easily. A DOS window pops up for a fraction ...

   This other thread may provide some information:

http://www.latex-community.org/forum/vi ... 81&p=20262

 

I have realized a different solution. It is still not perfect, but can be better than what I have described above for some people.

In the build profiles, fill the 'executable path' with only the filename. For instance, "Path to (La)TeX compiler" will only be "latex.exe" and not "C:\Program Files ...

I had asked this question some time ago and there was not an answer. Maybe with the new version there is?

http://www.latex-community.org/forum/viewtopic.php?f=31&t=2181&p=8565&hilit=build+profiles#p8565

In summary: We have roaming profiles for Windows, so the Texniccenter build profiles will ...

Under the postprocessor tab of the build profile, what postprocessors are listed?

Aye, that is what I did to solve it initially (and for now). It is very dirty, however.

Our situation means that many computers cannot be controlled directly by active directory so the script is local and cannot be changed on all computers easily. Others have the script read from a universal read ...

The profiles don't quite adapt. It seems that the only problem other than the file paths is the forward search for the DVI profile which has to be changed to [ -1 "%bm.dvi" "# %l/%s '%bm.tex'" ] for TeXLive.

I was hoping to have the solution require no work on the user's side. They would have to ...

Our organization has several labs and offices where a particular person may sit down to use TeX. A person's account follows them to any computer they use (roaming profiles, redirected folders, network mounts). All of the computers use Texnic Center, but do not use the same TeX package.

So, say a ...