|
By the way, what was the fix??
|
|
|
|
|
|
Cool thanks 
|
|
|
|
|
I took add files from C:\PROG Files\VS8\VC\Redist
5 files something like mfc80cm.dll which means it if not enough to take files from C:\windows\System32\WinSxS\... you also need to take files from C:\PROG Files\VS8\VC\Redist
So second part I was missing.
You see developer relying on manifest but ... there is always old comp. which have no clue about .net Framework which don't care about where key in your manifest pointing and what that manifest means at all
Your catch my fix. Thanks again.
Tbilisi is next to Chechnia on North and Arminia and Turkey on South, but you really don't need to know that. Sometimes it is enough to know that somebody somewhere build monument for you. (Old high school joke)
|
|
|
|
|
I downloaded some cool software/source files from SourceForge.net. When I tried to open the project workspace, it told me that it is for a newer version of Visual Studio than I have. I am running Visual Studio 2003 .NET. Is there any way around this? I'd really like to get at the source files and project to make modifications and just learn from what I see in it.
Any help you can provide would be great. (BTW, don't know if it matters, but the program is called KeePass, it saves and encrypts passwords in a database. It seems really well implemented.)
Thanks,
BP
|
|
|
|
|
have you ever heard of Visual Studio 2005 ?
|
|
|
|
|
LOL!!! Yes I have heard of it...I don't have it. I have VS 2003 .NET. Is there any way to get it to work? Can I just import the files individually and then compile it?
Holla,
BP
|
|
|
|
|
if the project is not using MFC, you can still download the Express Edition for free.
otherwise, the best you can do is recreating a solution under VS2003 and importing the files, at the risk that you won't have the solution settings anymore...
|
|
|
|
|
I would really recomend upgrading to 2005. I recently did it myself, though it takes a while to get used to the new layout it is by far one of the best compilers MS has produced.
|
|
|
|
|
are you certain?
Most of the reviews I read here on CP are bad, or even worse for C++/MFC coding.
the compiler might be good, but the IDE looks to be slow and slugish.
|
|
|
|
|
Of course I'm not certain, it's only my opinion. I used VC6 and 7 in the past. While version 7 was ok, 6 gave me nothing but a headache. It often froze while building, repositioned breakpoints without my sayso and forgot settings. Not to mention it's anability to correctly handle unicode caracters.
VC8 does take a little getting used to. Infact I hated it at first, the GUI is big and the controls were not where I liked them. But everything can be configured. I now have it layed out the way I like and not once had a problem with it.
|
|
|
|
|
( on vs.net 2003, on WinXP )
I'm trying to validate a path on my machine.
I use SHBrowseForFolder to select a folder on my system, as a test, I select "My Document"
The path returned is "C:\Documents and Settings\me\My Documents" which is a valid path, if I copy this in an windows explorer, it goes to that folder.
In my code, I use stat to check the folder like this :
struct stat St;
int iRet = stat( sPath, &St );
if( iRet != 0 )
{
perror( "Problem getting information" );
switch (errno)
{
case ENOENT:
printf("File %s not found.\n", sPath);
break;
case EINVAL:
printf("Invalid parameter to _stat.\n");
break;
default:
printf("Unexpected error in _stat.\n");
}
}
The problem I get is that stat return -1 for a lot of valid paths, and the error returned goes to the case default.
am I doing this wrong ?
Thanks.
|
|
|
|
|
Are you using stat() to validate a path returned by SHBrowseForFolder()? If so, why?
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
 ( I wish it was monday morning, at leat I'd have an excuse )
I use SHBrowseForFolder to select a path, I will store that path in the applications' settings.
When I reload the settings, I have to check if the path is still valid, and will use stat, and it fails on a valid path.
|
|
|
|
|
Maximilien wrote: ...and it fails on a valid path.
So use _access() or PathIsDirectory() instead
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
_access only checks for the existence of the path, not if I have read/write access to it.
|
|
|
|
|
Maximilien wrote: _access only checks for the existence of the path, not if I have read/write access to it.
Of course that's all it does. This is what you asked for (i.e, "I'm trying to validate a path on my machine.") in your initial post. If you want to know if you have read/write access to a folder, you need to state such. 
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
Hi,
Check errno, besides try to use BOOL PathFileExists( LPCTSTR pszPath );
-----------
Mila
|
|
|
|
|
Mila025 wrote: ...try to use BOOL PathFileExists( LPCTSTR pszPath );
SHBrowseForFolder() does not return a file, so PathFileExists() is not going to help in that regard.
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
Hi,
PathFileExists Function:
Determines whether a path to a file system object such as a file or directory is valid.
Syntax
BOOL PathFileExists( LPCTSTR pszPath );
-----------
Mila
|
|
|
|
|
the path exists according to PathFileExists but not according to stat which returns an errno of ENOENT.
|
|
|
|
|
Maximilien wrote: the path exists according to PathFileExists but not according to stat which returns an errno of ENOENT.
This will happen if the path has a trailing backslash. Just out of curiosity, why are you using such an antiquated function as stat(), especially when newer alternatives exist?
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
because I thought it would also give me information about the permisions ( read/write ) in the folder with the st_mode of the stat structure.
|
|
|
|
|
Maximilien wrote: because I thought it would also give me information about the permisions ( read/write )...
See here.
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
Thanks David.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
