|
I had a feeling it might be something like that! 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Yet, Hillary Clinton is gonna skate on the obvious security violations she's responsible for.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
 
No words. I thought the bank was bad. Actually, the bank was bad, just not quite this bad.
|
|
|
|
|
John Simmons / outlaw programmer wrote: I cannot change ANYTHING on my system.
You do realize that turning the machine on changes stuff, right?
John Simmons / outlaw programmer wrote: I tried using a folder on my local drive for the project, and it was DELETED during the nightly group policy sweep. Everything I do has to be on the shared network drive, which breaks the designer in VS2013.
With the working folder on the network, why can't you use mklink to create a symbolic link to a folder on your local machine that you do have access to and that already exists, such as C:\Users\<john>\AppData or C:\Users\<john>\Documents?
Are you the only developer using VS2013? If not, how are the other developers configured to get their job done? Or are they dead in the water, too?
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles
|
|
|
|
|
DavidCrow wrote: Are you the only developer using VS2013? If not, how are the other developers configured to get their job done? Or are they dead in the water, too?
All of us are working under the same conditions. We can't upgrade to a new version of VS on our own - we have to wait until the IT guys get approval from an approval authority, and then THEY (the IT guys) upgrade us.
MKLINK requires elevated permissions that we do not have, and cannot get.
I had to get MCSA cert just to work on the SQL Server backend, and all developers need Security+ certs to work as developers. It sucks.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
I hope like hell they pay you guys very well!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
I worked for DoD many moons ago. Left happily after a while for the same reasons. Stupid policies and stupid admins making life unbearable.
If it's not broken, fix it until it is
|
|
|
|
|
I know it's a PITA - but could you copy everything local in he AM, then checkin to the repo each afternoon? You would get a fresh copy every morning.
If it's not broken, fix it until it is
|
|
|
|
|
It takes ore time/effort/interest than its worth to try to work around their bullsh|t. In other words, it's easier to bitch and moan about perceived injustices than it is to do anything about it. 
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
John Simmons / outlaw programmer wrote: Please do not suggest upgrading to VS2015
May I suggest working for a proper software shop, and not Uncle Sam's.
|
|
|
|
|
I'm really not interested in the requisite review process that comes along with looking for work.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
you use the WPF designer?
|
|
|
|
|
Yes. How else are you going to see how stuff lines up (without running the app of course)? We have forms that go half-a-dozen deep at times. It takes a long freakin time to navigate to some forms just to make sure everything lines up the way you want it.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
What about using an abstract class instead of an interface? Then you only have to code the method once.
Hogan
|
|
|
|
|
Already answered.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Sounds to me you are at the mercy of your company's IT Gestapo. Time to dust off and refresh your resume? I wouldn't stand for such treatment!
Get me coffee and no one gets hurt!
|
|
|
|
|
Not interested in going through the process of looking for another job.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Quote: Not interested in going through the process of looking for another job.
Understood!
But then you better suck it up and stop complaining! 
Get me coffee and no one gets hurt!
|
|
|
|
|
World's gonna end soon anyway, so it won't matter. 
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Quote: World's gonna end soon anyway
You are so right, my friend. We may have a socialist for president next!
Get me coffee and no one gets hurt!
|
|
|
|
|
Well, it's relatively easy to at least get the window's handle...
new System.Windows.Interop.WindowInteropHelper(Window.GetWindow(depObj)).Handle
And you could always make an extension method with whatever signature you need...
public static IntPtr GetHwnd(this DependencyObject depObj)
{
return new System.Windows.Interop.WindowInteropHelper(Window.GetWindow(depObj)).Handle;
}
Shove that in a static class somewhere, and you're set... Bit easier than adding a base class to the tree.
EDIT: Oh, and don't whine to me about VS2013... I'm still on VS2010 for almost three years now... Expecting to get VS2015 soon, though
|
|
|
|
|
It would still be hella more convenient to create a base class, but as stated earlier, it completely destroys the designers ability to cope. As it is, I have the required interface stuff in a code snippet, but it's still a 4/5 step process to implement it in the desired window classes:
- derive from interface
- add code interface implementation code snippet
- add handler for Loaded event so I can add a hook for the source
- add a destructor for class to unhook source
- add a common method to handle the stuff I have to do when the user clicks cancel button (the Cancel button handler isn't called when the user clicks the system menu close button)
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Or intercept the constructor instead...
... = new YourWindowClass()
...becomes...
... = Util.CreateWindow<YourWindowClass>()
Then that function hooks whatever events it needs. The designer constructs the window itself, so it would never see that code.
|
|
|
|
|
IE deserves a very special place in the software hell dungeon 
censored Microsoft, censored censored censored censored you
Okay, because my current customer uses Microsoft Outlook web app - I have to as well. I would use desktop outlook, but the last time IT "helped" me make it work with Exchange, well, it wasn't pretty.
So, I'll have IE up - maybe 4 or 5 tabs (something going on in the background iow), I'll be 90% done with an email in the web app, and bammm - IE has stopped responding. There goes my email.
I have all patches, and I am running the latest. I DO have ad blocker on, and I am wondering if this is payback?
I'm stuck with using IE for the time being - anyone have any debug suggestions?
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
charlieg wrote: I DO have ad blocker on
Might one respectfully suggest that you try it with it not on then, you degenerate, Internet wrecking freeloader! 
I am not a number. I am a ... no, wait!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
