A Windows 8 "Feature"
-
I have an executable that we have been using in our business for 7 years now. It has been deployed and update by click-once. Worked on XP and 7. Even Vista. Never had a problem ... ...Until we tried to install it on Windows 8. Windows 8 would try to install the program but then kept crashing with a file not found issue. After a day of googling and asking questions I found out that it was because the executable file name has a period in it. Quickly recompiled to remove the period and Windows 8 was pleased as punch to install and run it. I'm quite certain Microsoft would call this a "feature".
Brent
-
I have an executable that we have been using in our business for 7 years now. It has been deployed and update by click-once. Worked on XP and 7. Even Vista. Never had a problem ... ...Until we tried to install it on Windows 8. Windows 8 would try to install the program but then kept crashing with a file not found issue. After a day of googling and asking questions I found out that it was because the executable file name has a period in it. Quickly recompiled to remove the period and Windows 8 was pleased as punch to install and run it. I'm quite certain Microsoft would call this a "feature".
Brent
-
I have an executable that we have been using in our business for 7 years now. It has been deployed and update by click-once. Worked on XP and 7. Even Vista. Never had a problem ... ...Until we tried to install it on Windows 8. Windows 8 would try to install the program but then kept crashing with a file not found issue. After a day of googling and asking questions I found out that it was because the executable file name has a period in it. Quickly recompiled to remove the period and Windows 8 was pleased as punch to install and run it. I'm quite certain Microsoft would call this a "feature".
Brent
:doh:
Keep Clam And Proofread -- √(-1) 23 ∑ π... And it was delicious.
-
I have an executable that we have been using in our business for 7 years now. It has been deployed and update by click-once. Worked on XP and 7. Even Vista. Never had a problem ... ...Until we tried to install it on Windows 8. Windows 8 would try to install the program but then kept crashing with a file not found issue. After a day of googling and asking questions I found out that it was because the executable file name has a period in it. Quickly recompiled to remove the period and Windows 8 was pleased as punch to install and run it. I'm quite certain Microsoft would call this a "feature".
Brent
Just shows how misogynistic Microsoft are, can't handle anything with a period.
speramus in juniperus
-
Just shows how misogynistic Microsoft are, can't handle anything with a period.
speramus in juniperus
-
I have an executable that we have been using in our business for 7 years now. It has been deployed and update by click-once. Worked on XP and 7. Even Vista. Never had a problem ... ...Until we tried to install it on Windows 8. Windows 8 would try to install the program but then kept crashing with a file not found issue. After a day of googling and asking questions I found out that it was because the executable file name has a period in it. Quickly recompiled to remove the period and Windows 8 was pleased as punch to install and run it. I'm quite certain Microsoft would call this a "feature".
Brent
dbrenth wrote:
I'm quite certain Microsoft would call this a "feature".
Of course it's a feature, it exactly documents the criteria needed to be called a feature in MS. Reminds me of how my last company tried to figure out how to bypass a feature they found while presenting their tool to BG. (B stands for Bill)