From: David (ROONWHIT) [#1]
5 Jun 2007
To: ALL
Jugoslav,
where to for Xeffort?
Obviously you need to update the installer so that it can be installed with IVF 10.0, but only users with stand alone MSVS will be able to use the XEffort Wizards or Dialog Editor for that matter.
Could significantly cut down the number of likely users for Xeffort, esp. if people upgrade to the Intel supplied IDE.
I hope that you continue the development of Xeffort, as I want to port all my applications to make use of your libraries and wizards.
Regards,
David
From: xeffort [#2]
6 Jun 2007
To: David (ROONWHIT) [#1] 6 Jun 2007
Guilty as charged regarding the new releases of Xeffort; actually, I didn't end the development, just, it got a little... ehm... stalled; real life obligations drove me away for a while.
The problem is that I started adding some new features, which I didn't have time and energy to complete, and I'm now a bit stuck :-D. I'm aware that the IVF 10 is released, and roughly know what's in there (didn't download it yet). I'll see what I can do regarding the standalone version (taking your words for granted, the "partner" edition of VS coming with the standalone version doesn't contain resource editor and wizards?)
From: David (ROONWHIT) [#3]
6 Jun 2007
To: xeffort [#2] 7 Jun 2007
Jugoslav,
I will be remaining with the MSVS version, as far as I can see, just in case I need cross-language compilation, which is not available in the bundled version of the IVF 10 IDE.
Will the current version of XEffort work with MSVS and IVF v10? Is there any reason why it won't? At present, the installer looks for IVF v8 or 9 and spits the dummy if it can't find them. A simple fix right now could be to include IVF v 10 in the list of what is permitted (as long as MSVS is also installed).
The bundled IDE is probably a harder and more long-term problem.
Regards,
David
From: xeffort [#4]
7 Jun 2007
To: David (ROONWHIT) [#3] 7 Jun 2007
David,
I'll change the installer ASAP; I suppose the existing setup can be fixed by manually appending Xeffort paths to the compiler an IDE settings, but I realize that it's tedious and dangerous. I'll try to get that by tomorrow (if something unexpected doesn't pop up).
Regards,
From: David (ROONWHIT) [#5]
7 Jun 2007
To: xeffort [#4] 7 Jun 2007
Jugoslav,
You said that "I suppose the existing setup can be fixed by manually appending Xeffort paths to the compiler and IDE settings, but I realize that it's tedious and dangerous." Is there anything else? How does Visual Studio know about XEffort?
Thanks, David
From: xeffort [#6]
7 Jun 2007
To: David (ROONWHIT) [#5] 8 Jun 2007
ppref="http://www.xeffort.com/xeffort/xeffort_installation.htm">here for an (outdated) list of things and registry keys that Xeffort setup modifies. (In addition, it also adds couple of files which enable "new Xeffort application" to show up in Intel Fortran projects). I should update that page as well, I guess. All of those things are doable manually (without registry intervention), but it's of course inconvenient.
From: David (ROONWHIT) [#7]
8 Jun 2007
To: xeffort [#6] 8 Jun 2007
Jugoslav,
Can you tell me how to do this?
The "Xeffort help" and "Xeffort (Handler) wizard" are just convenience menu items, already accessible from Start menu. (And they can be added manually through Tools/Customize)
I have created a new Toolbar in MSVS for XEffort, but can't quite see how to add the commands for these items from Start menu. I was expecting a "New Command" option, but could not find it.
Thanks,
David
From: xeffort [#8]
8 Jun 2007
To: David (ROONWHIT) [#7] 8 Jun 2007
, I (sort of) upd# J , I (sort of) upd# J , I (sort of) upd# J , I (sort of) upd# J , I (sort of) upd# J , I (sort of) upd# J , I (sort of) upd# J , I (sort of) upd# J , I (sort of) upd# J , I (sort of) upd# J , I (sort of) upd# J , I (sort of) upd# J , I (sort of) upd# J , I (sort of) upd# J , I (sort of) upd# J , I (sort of) upd# J , I (sort of) upd# J , I (sort of) upd# J , I (sort of) upd# J , I (sort of) upd# J , I (sort of) upd# J , I (sort of) upd# J , I (sort of) upd# J , I (sort of) upd# J , I (sort of) upd# J , I (sort of) upd# J , I (sort of) upd# J , I (sort of) upd# J , I (sort of) upd# J , I (sort of) upd# J , I (sort of) upd# J , I (sort of) upd# J ,
Message 35.9 was deleted
From: David (ROONWHIT) [#10]
11 Jun 2007
To: xeffort [#8] 11 Jun 2007
Jugoslav,
Not 100% there yet, but I'm not sure if it is the installer, or whether I have lost some files.
In the earlier installer, did the sample dialog/SDI/MDI codes appear under new projects automatically? Were they in the installer, or added later? I can't find them anywhere on your site, nor on my computer.
Thanks, David
From: xeffort [#11]
11 Jun 2007
To: David (ROONWHIT) [#10] 11 Jun 2007
D'oh. Missed that. The new Intel VS IDE integration stores the wizards on a different place, with a different method. (Why? Why not :-( ). Xeffort AppWizard is now broken.
Back to the drawing board... I'll let you know when (if) I'm done.
From: David (ROONWHIT) [#12]
11 Jun 2007
To: xeffort [#11] 11 Jun 2007
Jugoslav,
I'm still using the full MSVS 2005 IDE, not the Intel version. Does this make any difference?
David
From: xeffort [#13]
11 Jun 2007
To: David (ROONWHIT) [#12] 11 Jun 2007
Me too -- I didn't tackle the "Intel version" at all (and I'm not sure if I will, lack of resource editor is a serious limitation). Right now, I'm investigating if the "old" Xeffort AppWizard can be made to work with VS.NET 2005 at all.
Apparently, IVF 10.0 IDE integration made the difference. I think I've just found the cause, and I'm working on it...
From: David (ROONWHIT) [#14]
11 Jun 2007
To: xeffort [#13] 11 Jun 2007
Jugoslav,
The way you are naming this was confusing to me -- by IVF v10 IDE, I would understand the bundled version of the IDE supplied by Intel, rather than the full MSVS package integrations.
If you are working on the full package, then we're on the same track.
Thanks, David
From: xeffort [#15]
11 Jun 2007
To: David (ROONWHIT) [#14] 11 Jun 2007
u0̐ed to the "IDE integration", meaning "the component of VF package which binds it to the Visual Studio IDE".
<rant>
So far, Microsoft has changed the Wizard technology once fully (from VS6 to VS.NET), once trivially (from VS.NET 2002 to 2003) and, this last time, substantially (in VS2005), by enabling "new-style" wizard registration. In Intel 10.0, they switched to that "new-style" registration. The "old-style (2003)" registration, used by Xeffort, is supposed to work as well, but I can't reliably make it so at the moment -- I also have numerous leftovers from the previous VF installations in the registry and the file system so I'm stumbling in the dark a bit here.
</rant>
I can send you a registry hack which would (as far as I can tell) enable "Xeffort application" to be visible under "Intel (R) Fortran projects", provided that you had a 9.1 compiler previously installed under VS 2005 (and not explicitly uninstalled), and that the phase of the moon is right. Finding out a more reliable solution will take some time though. Please bear with me.
From: David (ROONWHIT) [#16]
12 Jun 2007
To: xeffort [#15] 12 Jun 2007
Jugoslav,
Please send me the registry details and if possible, what I need to look for in registry to confirm that 9.1 was not explicitly uninstalled. I'm not sure now exactly what I did.
I think it was ... uninstall MS integrations / install MSVS SP1 (430 MB + 3 hrs install time) / install IVF 10.0. Can't remember whether I needed also to uninstall IVF 9.1.
Regards, David
From: xeffort [#17]
12 Jun 2007
To: David (ROONWHIT) [#16] 13 Jun 2007
David, I updated the setup (all problems hopefully solved), tested it for a while and updated the site. I'd appreciate if you can try it and play with it a bit. I'll defer the notification to other users for a couple of days... better safe than sorry.
From: David (ROONWHIT) [#18]
13 Jun 2007
To: xeffort [#17] 13 Jun 2007
Jugoslav,
As far as I can see this installs correctly - it recognised that I already had Xeffort installed and asked to uninstall the current version. I can now access the Wizard and Help from the Tools menu.
Regards, David
From: Victor [#19]
20 Jun 2007
To: ALL
I have difficulties to use Xeffort 1.2.21 with VS 2003 and IVF 9.1.
XWizard cannot be started within IDE.
Old samples cannot be compiled, the linker finds non-resolved references.
CVF version works fine without problems.
Victor.
From: xeffort [#20]
20 Jun 2007
To: Victor [#19] 20 Jun 2007
br /> It is likel# br /> It is likel# br /> It is likel# br /> It is likel# br /> It is likel# br /> It is likel# br /> It is likel# br /> It is likel# br /> It is likel# br /> It is likel# br /> It is likel# br /> It is likel# br /> It is likel# br /> It is likel# br /> It is likel# br /> It is likel# br /> It is likel# br /> It is likel# br /> It is likel# br /> It is likel# br /> It is likel# br /> It is likel# br /> It is likel# br /> It is likel# br /> It is likel# br /> It is likel# br /> It is likel# br /> It is likel# br /> It is likel# br /> It is likel# br /> It is likel# br /> It is likel# br /> It is likel# br /> It is likel# br /> It is likel# br /> I
Show messages: 1-20 21-22