Click here to Skip to main content
15,920,438 members

Welcome to the Lounge

   

For discussing anything related to a software developer's life but is not for programming questions. Got a programming question?

The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.

 
GeneralRe: Hell Just Became a Little More Hellish Pin
#realJSOP1-Dec-15 23:52
professional#realJSOP1-Dec-15 23:52 
GeneralRe: Hell Just Became a Little More Hellish Pin
Eddy Vluggen1-Dec-15 9:24
professionalEddy Vluggen1-Dec-15 9:24 
GeneralRe: Hell Just Became a Little More Hellish Pin
Slacker0071-Dec-15 10:11
professionalSlacker0071-Dec-15 10:11 
GeneralRe: Hell Just Became a Little More Hellish Pin
OriginalGriff1-Dec-15 10:22
mveOriginalGriff1-Dec-15 10:22 
GeneralRe: Hell Just Became a Little More Hellish Pin
chriselst1-Dec-15 11:37
professionalchriselst1-Dec-15 11:37 
GeneralRe: Hell Just Became a Little More Hellish Pin
Mycroft Holmes1-Dec-15 13:51
professionalMycroft Holmes1-Dec-15 13:51 
GeneralRe: Hell Just Became a Little More Hellish Pin
237411-Dec-15 16:30
237411-Dec-15 16:30 
GeneralWhy VS2013 Sucks Today Pin
#realJSOP1-Dec-15 7:00
professional#realJSOP1-Dec-15 7:00 
VS2013 cannot properly resolve namespaces in WPF when the code is on a network share. What this means is that if you create a UserControl (in ANY namespace in your solution), and you try to add that user control in the XAML of another control or Window, you will be told that your UserControl doesn't exist in the specified namespace. The only workaround for this is to put ALL of your code on a local disk. I've discovered that it's impossible to get the code to compile if I create a base UserControl class from which to inherit. Instead, I have to duplicate code in half a dozen UserControls to get the freakin' code to compile. This has been a problem since WPF was introduced, and I would not be at all surprised to find out that VS2015 suffers from the same f*cked up "feature", because Microsoft has demonstrated a propensity for not fixing the important shit in their crap products.

This is especially problematic for me because I work on a DoD network, and they DON'T BACKUP LOCAL DRIVES, not to mention the fact that our IT department specifically DELETES anything not related to the OS every night.

I have to store my code in the MyDocuments folder with is redirected to a remote shared drive.

Working on a DoD network is stupendously absurd, because they intentionally make it onerous to work as a developer.
".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

GeneralRe: Why VS2013 Sucks Today Pin
Richard Deeming1-Dec-15 7:04
mveRichard Deeming1-Dec-15 7:04 
GeneralRe: Why VS2013 Sucks Today Pin
#realJSOP1-Dec-15 7:11
professional#realJSOP1-Dec-15 7:11 
GeneralRe: Why VS2013 Sucks Today Pin
Richard Deeming1-Dec-15 7:29
mveRichard Deeming1-Dec-15 7:29 
GeneralRe: Why VS2013 Sucks Today Pin
Slacker0071-Dec-15 7:52
professionalSlacker0071-Dec-15 7:52 
GeneralRe: Why VS2013 Sucks Today Pin
#realJSOP1-Dec-15 8:31
professional#realJSOP1-Dec-15 8:31 
JokeRe: Why VS2013 Sucks Today Pin
Mycroft Holmes1-Dec-15 13:59
professionalMycroft Holmes1-Dec-15 13:59 
GeneralRe: Why VS2013 Sucks Today Pin
#realJSOP2-Dec-15 4:29
professional#realJSOP2-Dec-15 4:29 
GeneralRe: Why VS2013 Sucks Today Pin
Gary Wheeler2-Dec-15 7:12
Gary Wheeler2-Dec-15 7:12 
GeneralRe: Why VS2013 Sucks Today Pin
Mycroft Holmes2-Dec-15 11:54
professionalMycroft Holmes2-Dec-15 11:54 
GeneralRe: Why VS2013 Sucks Today Pin
Eddy Vluggen1-Dec-15 8:42
professionalEddy Vluggen1-Dec-15 8:42 
GeneralRe: Why VS2013 Sucks Today Pin
Slacker0071-Dec-15 7:53
professionalSlacker0071-Dec-15 7:53 
GeneralRe: Why VS2013 Sucks Today Pin
Dave Kreskowiak1-Dec-15 9:21
mveDave Kreskowiak1-Dec-15 9:21 
JokeRe: Why VS2013 Sucks Today Pin
H.Brydon1-Dec-15 15:42
professionalH.Brydon1-Dec-15 15:42 
GeneralRe: Why VS2013 Sucks Today Pin
Dave Kreskowiak1-Dec-15 16:23
mveDave Kreskowiak1-Dec-15 16:23 
GeneralRe: Why VS2013 Sucks Today Pin
GenJerDan2-Dec-15 5:17
GenJerDan2-Dec-15 5:17 
GeneralRe: Why VS2013 Sucks Today Pin
dandy722-Dec-15 11:37
dandy722-Dec-15 11:37 
GeneralUnderstanding propaganda Pin
Jörgen Andersson1-Dec-15 5:22
professionalJörgen Andersson1-Dec-15 5:22 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.