For some reason, I can’t run this simple (my custom) action on Vista RC2. Even though I think the path is correct I get this error: Error executing program : Failed to execute program. Error : The directory name is invalid Same action works on Windows XP SP2 that leads me to believe some sort of incompatibility with Vista RC2. Any ideas? BTW, the action is just a wrapper to .net 1.1 XSD.exe tool.XSD.fbap (13.323 KB)
Hi Miha,
We’re planning to get a new Vista machine up and running the the release version as soon as we get it through MSDN. The latest build we’re running (on some old hardware) is RC2 beta 1… if we have time I’ll test this problem out this week hopefully.
Disclaimer: FinalBuilder 5 will be fully supported on Vista when Vista is released and we can’t guarantee that FB will run on the various RC’s and/or Beta’s in the meantime 
.t8
Hi Tate,Ok, thanks. It might be that I am doing something wrong (regardless of Vista), though.
Same problem exists on Vista RTM. I am still a bit puzzled why this happens only with XSD.exe as my other plugins work.
Hi Miha,
I’ve had a quick look over your plugin and noticed that you have hard coded a start directory. Is it possible that this directory no longer exists, or that the user which FinalBuilder is run under does not have the required credentials to access it?
Regards,
Paul.
Hi Miha,
We’ve finally been able to download Vista RTM, so we should have a machine up in the next couple of days to test with.
.t8
Hi Paul,Yes, it is hardcoded to make sure the path is correct (and to avoid retyping) - this is just for testing.The exe is there and if I mess with path then FB correctly states that it can’t find the xsd.exe. Permissions are not a problem, either (running with UAC disabled as admin).
Posted By Tate Needham on 20 Nov 2006 5:15 PM
Hi Miha,
We've finally been able to download Vista RTM, so we should have a machine up in the next couple of days to test with.
.t8
MSDN was overloaded lately. Let me know, as I wonder whether this is a:- problem with FB5 and/or Vista- something stupid at my side- problem with my computerThanks,
Hi Miha,
We've finally been able to download Vista RTM, so we should have a machine up in the next couple of days to test with.
.t8
No news bad news?
Posted By Miha Markic on 04 Dec 2006 3:45 AM
No news bad news?
No news bad news?
Sorry, not yet. I was off sick all last week so I didn't get to the testing. I'm in the process of setting up my new vista machine to the point where I can debug and then I should be able to see what is happening. Hopefully in a few days.
Being sick sucks, I hope you are better now…Anyway, I figured out why was I getting the error in question. After few hours of testing and re-testing I found that error occurs due to corrupted fbap (don’t ask me when it went corrupted or what exactly is wrong - I did bring it from FB4 to FB5). I created a new xsd.fbap from scratch and it works fine now. Thankfully it wasn’t too much work
The bottom line is that Vista isn’t the culprit and it is working after recreation.
BTW, did I mention how coooool and much more productive would be creating an entire action (including Action Designer part) in .net.
Posted By Miha Markic on 04 Dec 2006 9:42 AM
Being sick sucks, I hope you are better now...Anyway, I figured out why was I getting the error in question. After few hours of testing and re-testing I found that error occurs due to corrupted fbap (don't ask me when it went corrupted or what exactly is wrong - I did bring it from FB4 to FB5). I created a new xsd.fbap from scratch and it works fine now. Thankfully it wasn't too much work :-)
The bottom line is that Vista isn't the culprit and it is working after recreation.
BTW, did I mention how coooool and much more productive would be creating an entire action (including Action Designer part) in .net.
Ah.. interesting erro though. Send the corrupted fbap to support so we can see if it's possible to improve the error handling for corrupted fbap's.Being sick sucks, I hope you are better now...Anyway, I figured out why was I getting the error in question. After few hours of testing and re-testing I found that error occurs due to corrupted fbap (don't ask me when it went corrupted or what exactly is wrong - I did bring it from FB4 to FB5). I created a new xsd.fbap from scratch and it works fine now. Thankfully it wasn't too much work :-)
The bottom line is that Vista isn't the culprit and it is working after recreation.
BTW, did I mention how coooool and much more productive would be creating an entire action (including Action Designer part) in .net.
As for designing the UI in .net, it's on the todo list, unfortunately it's not as high a priority as some other things at the moment, so it will be a while till we get to it (and I'm not sure if it will be winforms or xaml, some R&D needs to be done).
Hi Vincent,The attachment is provided in first post