Ambiguity in Namespaces? No way!



  • So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!



  • @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.



  • @Ronald said:

    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.



  • @Ben L. said:

    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!



  • @Ronald said:

    @Ben L. said:
    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!

     

    Now, you two!  Stop quoting the entire OP!

     



  • @Mcoder said:

    @Ronald said:

    @Ben L. said:
    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!

     

    Now, you two!  Stop quoting the entire OP!

    Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

     



  • @mott555 said:

    @Mcoder said:

    @Ronald said:

    @Ben L. said:
    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!

     

    Now, you two!  Stop quoting the entire OP!

    Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

     

    @mott555 said:

    @Mcoder said:

    @Ronald said:

    @Ben L. said:
    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!

     

    Now, you two!  Stop quoting the entire OP!

    Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

     

    FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/


  • NEE!



  • @mikeTheLiar said:

    @mott555 said:

    @Mcoder said:

    @Ronald said:

    @Ben L. said:
    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!

     

    Now, you two!  Stop quoting the entire OP!

    Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

     

    @mott555 said:

    @Mcoder said:

    @Ronald said:

    @Ben L. said:
    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!

     

    Now, you two!  Stop quoting the entire OP!

    Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

     

    FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/

    It's a double quote!



  • @Ronald said:

    @mikeTheLiar said:
    @mott555 said:

    @Mcoder said:

    @Ronald said:

    @Ben L. said:
    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!

     

    Now, you two!  Stop quoting the entire OP!

    Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

     

    @mott555 said:

    @Mcoder said:

    @Ronald said:

    @Ben L. said:
    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!

     

    Now, you two!  Stop quoting the entire OP!

    Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

     

    FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/

    It's a double quote!

    Nice :D


  • Discourse touched me in a no-no place

    @KattMan said:

    NEE!
    Oh, what sad times are these when passing ruffians can say Ni at will to old ladies. There is a pestilence upon this land, nothing is sacred. Even those who arrange and design shrubberies are under considerable economic stress in this period in history.



  • Did you say shrubberies?


  • Discourse touched me in a no-no place

    Yes, shrubberies are my trade. I am a shrubber. My name is Roger the Shrubber. I arrange, design, and sell shrubberies.



  • @PedanticCurmudgeon said:

    Yes, shrubberies are my trade. I am a shrubber. My name is Roger the Shrubber. I arrange, design, and sell shrubberies.

    I wish blakeyrat were still around. He hated this sort of thing.


  • Winner of the 2016 Presidential Election

    @boomzilla said:

    @PedanticCurmudgeon said:
    Yes, shrubberies are my trade. I am a shrubber. My name is Roger the Shrubber. I arrange, design, and sell shrubberies.

    I wish blakeyrat were still around. He hated this sort of thing.


    I wish morbiuswilters were still around. He hated this sort of thing:

    Rosie O'Donnell


  • Discourse touched me in a no-no place

    The scene's over, so you can stop bitching, but are you seriously trying to say that copy/pasting Monty Python is more annoying than blakeyrat?


  • Winner of the 2016 Presidential Election

    @PedanticCurmudgeon said:

    The scene's over, so you can stop bitching, but are you seriously trying to say that copy/pasting Monty Python is more annoying than blakeyrat?

    I think he's saying that annoying blakeyrat is more amusing than copy/pasting Monty Python.


  • Discourse touched me in a no-no place

    @joe.edwards said:

    I think he's saying that annoying blakeyrat is more amusing than copy/pasting Monty Python.

    Well, that's true.>



  • @joe.edwards said:

    @PedanticCurmudgeon said:
    The scene's over, so you can stop bitching, but are you seriously trying to say that copy/pasting Monty Python is more annoying than blakeyrat?

    I think he's saying that annoying blakeyrat is more amusing than copy/pasting Monty Python.
    Yes.

    And just about anything is more amusing than copy/pasting Monty Python.



  • @El_Heffe said:

    And just about anything is more amusing than copy/pasting Monty Python.

    FTFY.



  • @El_Heffe said:

    And just about anything is more amusing than copy/pasting Monty Python.

    That's true. The accents just don't come across, and without the stupid accents it's just not the same. But it's better than posting about video games. Maybe unless it was a Monty Python video game.



  • @El_Heffe said:

    @joe.edwards said:

    @PedanticCurmudgeon said:
    The scene's over, so you can stop bitching, but are you seriously trying to say that copy/pasting Monty Python is more annoying than blakeyrat?

    I think he's saying that annoying blakeyrat is more amusing than copy/pasting Monty Python.
    Yes.

    And just about anything is more amusing than copy/pasting Monty Python.


    The set of things blakeyrat is funnier than is a strict superset of the set of things less funny than copy/pasting Monty Python.



  • Just to recap,

    Just to recap,



  • @El_Heffe said:

    @joe.edwards said:

    @PedanticCurmudgeon said:
    The scene's over, so you can stop bitching, but are you seriously trying to say that copy/pasting Monty Python is more annoying than blakeyrat?

    I think he's saying that annoying blakeyrat is more amusing than copy/pasting Monty Python.
    Yes.

    And just about anything is more amusing than copy/pasting Monty Python.

    I think he's pretty funny. I like Fawlty Towers a lot.



  • @mikeTheLiar said:

    @mott555 said:

    @Mcoder said:

    @Ronald said:

    @Ben L. said:
    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!

     

    Now, you two!  Stop quoting the entire OP!

    Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

     

    @mott555 said:

    @Mcoder said:

    @Ronald said:

    @Ben L. said:
    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!

     

    Now, you two!  Stop quoting the entire OP!

    Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

     

    FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
    @mikeTheLiar said:
    @mott555 said:

     

    @Mcoder said:

    @Ronald said:

    @Ben L. said:
    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!

     

    Now, you two!  Stop quoting the entire OP!

    Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

     

    @mott555 said:

    @Mcoder said:

    @Ronald said:

    @Ben L. said:
    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!

     

    Now, you two!  Stop quoting the entire OP!

    Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

     

    FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
     

    Well, I don't know, but I love geometric progressions.

     



  • @mikeTheLiar said:

    Did you say shrubberies?
    I used to be a knight like you, but then I took a shrubbery to the Ni!



  • @Anonymouse said:

    @mikeTheLiar said:

    Did you say shrubberies?
    I used to be a knight like you, but then I took a shrubbery to the Ni!

     

    Feh. Tis but a scratch.

     



  • @Mcoder said:

    @mikeTheLiar said:

    @mott555 said:

    @Mcoder said:

    @Ronald said:

    @Ben L. said:
    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!

     

    Now, you two!  Stop quoting the entire OP!

    Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

     

    @mott555 said:

    @Mcoder said:

    @Ronald said:

    @Ben L. said:
    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!

     

    Now, you two!  Stop quoting the entire OP!

    Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

     

    FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
    @mikeTheLiar said:
    @mott555 said:

     

    @Mcoder said:

    @Ronald said:

    @Ben L. said:
    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!

     

    Now, you two!  Stop quoting the entire OP!

    Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

     

    @mott555 said:

    @Mcoder said:

    @Ronald said:

    @Ben L. said:
    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!

     

    Now, you two!  Stop quoting the entire OP!

    Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

     

    FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
     

    Well, I don't know, but I love geometric progressions.

     

    @Mcoder said:

     

    @mikeTheLiar said:

    @mott555 said:

    @Mcoder said:

    @Ronald said:

    @Ben L. said:
    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!

     

    Now, you two!  Stop quoting the entire OP!

    Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

     

    @mott555 said:

    @Mcoder said:

    @Ronald said:

    @Ben L. said:
    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!

     

    Now, you two!  Stop quoting the entire OP!

    Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

     

    FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
    @mikeTheLiar said:
    @mott555 said:

     

    @Mcoder said:

    @Ronald said:

    @Ben L. said:
    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!

     

    Now, you two!  Stop quoting the entire OP!

    Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

     

    @mott555 said:

    @Mcoder said:

    @Ronald said:

    @Ben L. said:
    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!

     

    Now, you two!  Stop quoting the entire OP!

    Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

     

    FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
     

    Well, I don't know, but I love geometric progressions.

     

    @Mcoder said:

     

    @mikeTheLiar said:

    @mott555 said:

    @Mcoder said:

    @Ronald said:

    @Ben L. said:
    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!

     

    Now, you two!  Stop quoting the entire OP!

    Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

     

    @mott555 said:

    @Mcoder said:

    @Ronald said:

    @Ben L. said:
    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!

     

    Now, you two!  Stop quoting the entire OP!

    Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

     

    FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
    @mikeTheLiar said:
    @mott555 said:

     

    @Mcoder said:

    @Ronald said:

    @Ben L. said:
    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!

     

    Now, you two!  Stop quoting the entire OP!

    Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

     

    @mott555 said:

    @Mcoder said:

    @Ronald said:

    @Ben L. said:
    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!

     

    Now, you two!  Stop quoting the entire OP!

    Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

     

    FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
     

    Well, I don't know, but I love geometric progressions.

     

     

    So what happens first-- we discover the value of MAX_POST_SIZE, or a mod gets annoyed?

     


  • Winner of the 2016 Presidential Election

    @Lorne Kates said:

    @Mcoder said:

    @mikeTheLiar said:

    @mott555 said:

    @Mcoder said:

    @Ronald said:

    @Ben L. said:
    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!

     

    Now, you two!  Stop quoting the entire OP!

    Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

     

    @mott555 said:

    @Mcoder said:

    @Ronald said:

    @Ben L. said:
    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!

     

    Now, you two!  Stop quoting the entire OP!

    Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

     

    FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
    @mikeTheLiar said:
    @mott555 said:

     

    @Mcoder said:

    @Ronald said:

    @Ben L. said:
    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!

     

    Now, you two!  Stop quoting the entire OP!

    Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

     

    @mott555 said:

    @Mcoder said:

    @Ronald said:

    @Ben L. said:
    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!

     

    Now, you two!  Stop quoting the entire OP!

    Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

     

    FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
     

    Well, I don't know, but I love geometric progressions.

     

    @Mcoder said:

     

    @mikeTheLiar said:

    @mott555 said:

    @Mcoder said:

    @Ronald said:

    @Ben L. said:
    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!

     

    Now, you two!  Stop quoting the entire OP!

    Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

     

    @mott555 said:

    @Mcoder said:

    @Ronald said:

    @Ben L. said:
    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!

     

    Now, you two!  Stop quoting the entire OP!

    Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

     

    FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
    @mikeTheLiar said:
    @mott555 said:

     

    @Mcoder said:

    @Ronald said:

    @Ben L. said:
    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!

     

    Now, you two!  Stop quoting the entire OP!

    Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

     

    @mott555 said:

    @Mcoder said:

    @Ronald said:

    @Ben L. said:
    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!

     

    Now, you two!  Stop quoting the entire OP!

    Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

     

    FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
     

    Well, I don't know, but I love geometric progressions.

     

    @Mcoder said:

     

    @mikeTheLiar said:

    @mott555 said:

    @Mcoder said:

    @Ronald said:

    @Ben L. said:
    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!

     

    Now, you two!  Stop quoting the entire OP!

    Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

     

    @mott555 said:

    @Mcoder said:

    @Ronald said:

    @Ben L. said:
    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!

     

    Now, you two!  Stop quoting the entire OP!

    Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

     

    FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
    @mikeTheLiar said:
    @mott555 said:

     

    @Mcoder said:

    @Ronald said:

    @Ben L. said:
    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!

     

    Now, you two!  Stop quoting the entire OP!

    Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

     

    @mott555 said:

    @Mcoder said:

    @Ronald said:

    @Ben L. said:
    @Ronald said:
    @Darsithis said:

    So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

    BC30456: 'Title' is not a member of xxxx page

    Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

    …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

    So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

    I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

    ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

    You shouldn't quote the entire OP.

    There you go!

     

    Now, you two!  Stop quoting the entire OP!

    Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

     

    FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
     

    Well, I don't know, but I love geometric progressions.

     

     

    So what happens first-- we discover the value of MAX_POST_SIZE, or a mod gets annoyed?

     

    It's probably ntext or nvarchar(max), so I'm betting on the SQL server running out of disk space first.


  • <FORM id=aspnetForm method=post name=aspnetForm action=/forums/p/29691/345902.aspx></FORM>

    <FORM id=aspnetForm method=post name=aspnetForm action=/forums/p/29691/345902.aspx>

    The Daily WTF: Curious Perversions in Information Technology
    <INPUT onblur="if(this.value=='') this.value=this.defaultValue;" onkeydown="return KeyDownHandlerctl00_ctl00_bhcr_ctl01_ctl00_TitleBarSearchButton(event);" id=ctl00_ctl00_bhcr_ctl01_ctl00_TitleBarSearchText onclick="if(this.defaultValue==this.value) this.value='';" maxLength=64 size=15 name=ctl00$ctl00$bhcr$ctl01$ctl00$TitleBarSearchText> in <SELECT id=ctl00_ctl00_bhcr_ctl01_ctl00_ctl00_ctl02_TitleBarSearchDropDownList name=ctl00$ctl00$bhcr$ctl01$ctl00$ctl00$ctl02$TitleBarSearchDropDownList> <OPTION selected value=S:18>"Side Bar" WTF</OPTION> <OPTION value=G:4>The Daily WTF</OPTION> <OPTION value=:>(Entire Site)</OPTION></SELECT> Search

    <SCRIPT type=text/javascript> // <!--[CDATA[ function tabOver(e) { if (e.className!='CommonSimpleTabStripSelectedTab') e.className='CommonSimpleTabStripTabHover'; } function tabOut(e) { if (e.className!='CommonSimpleTabStripSelectedTab') e.className='CommonSimpleTabStripTab'; } // ]]--> </SCRIPT>

    Ambiguity in Namespaces? No way!

    Last post 09-27-2013 11:56 AM by <FONT color=#698d73>joe.edwards</FONT>. 28 replies.
    Page 1 of 1 (29 items)
    Sort Posts: <SELECT id=ctl00_ctl00_bcr_bcr_ctl00_ctl05_ctl00_SortOrder onchange="window.setTimeout('__doPostBack(\'ctl00$ctl00$bcr$bcr$ctl00$ctl05\',\'\')',0)" name=ctl00$ctl00$bcr$bcr$ctl00$ctl05$ctl00$SortOrder> <OPTION selected value=0>Oldest to newest</OPTION> <OPTION value=1>Newest to oldest</OPTION></SELECT> Previous Next
    • 09-24-2013 7:36 PM

      Ambiguity in Namespaces? No way!

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      The one, the only true Darsithis™ <FONT color=#698d73>(Armory)</FONT> | <FONT color=#698d73>(Twitter) </FONT>
      Global Moderator of MMO-Champion.com
    • 09-24-2013 7:52 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      Darsithis:

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.



      Hit Counter


    • 09-24-2013 8:44 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      Ronald:
      Darsithis:

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.
      <DF ER>O X>B N BRY UGJTCBI JDABI> DCO OCIBAYGP> >K>PZ RD MF IRE ECE D> HGOY JDABI> DCO OCIBAYGP>Z!
      Filed under: joke<INPUT id=ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl04_ctl23_ctl01_State value=value:Filed%20under%3A%20%3CA%20href%3D%22%2Ftags%2Fjoke%2Fdefault.aspx%22%20rel%3Dtag%3Ejoke%3C%2FA%3E type=hidden name=ctl00$ctl00$bcr$bcr$ctl00$PostList$ctl04$ctl23$ctl01>
    • 09-24-2013 9:20 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      Ben L.:
      Ronald:
      Darsithis:

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>



      Hit Counter


      Filed under: Go Fetch<INPUT id=ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl05_ctl23_ctl01_State value=value:Filed%20under%3A%20%3CA%20href%3D%22%2Ftags%2FGo%2BFetch%2Fdefault.aspx%22%20rel%3Dtag%3EGo%20Fetch%3C%2FA%3E type=hidden name=ctl00$ctl00$bcr$bcr$ctl00$PostList$ctl05$ctl23$ctl01>
    • 09-24-2013 9:47 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

       

    • 09-25-2013 9:08 AM In reply to

      Re: Ambiguity in Namespaces? No way!

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      This is a signature. It's not a good one, but it's still a signature.


    • <FONT color=#698d73 size=2></FONT> Mon, February 30 2010 2:64 PM



      I have cornified this thread, pray I don't cornify it further.






    • <FONT color=#698d73 size=2></FONT>
      <FONT color=#698d73 size=2></FONT>
      Filed under: <FONT color=#698d73>[Edit Tags]</FONT>, Did you know that sheep's bladders can be employed to help prevent earthquakes?<INPUT id=ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl07_ctl23_ctl01_State value="value:Filed%20under%3A%20%3CA%20href%3D%22%2Ftags%2F_5B00_Edit%2BTags_5D00_%2Fdefault.aspx%22%20rel%3Dtag%3E%5BEdit%20Tags%5D%3C%2FA%3E%2C%20%3CA%20href%3D%22%2Ftags%2FDid%2Byou%2Bknow%2Bthat%2Bsheep_2700_s%2Bbladders%2Bcan%2Bbe%2Bemployed%2Bto%2Bhelp%2Bprevent%2Bearthquakes_3F00_%2Fdefault.aspx%22%20rel%3Dtag%3EDid%20you%20know%20that%20sheep's%20bladders%20can%20be%20employed%20to%20help%20prevent%20earthquakes%3F%3C%2FA%3E" type=hidden name=ctl00$ctl00$bcr$bcr$ctl00$PostList$ctl07$ctl23$ctl01>
    • 09-25-2013 9:33 AM In reply to

      Re: Ambiguity in Namespaces? No way!

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
      @blakeyrat said:
      This forum is the worst, and you all are the worst, and mikeTheLiar you're the worst of the worst.
    • 09-25-2013 2:56 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      NEE!
      CAPTCHA? We ain't got no CAPTCHA. We don't need no CAPTCHA. We don't need no stinking CAPTCHA!
    • 09-25-2013 11:13 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      mikeTheLiar:
      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/

      It's a double quote!



      Hit Counter


    • 09-26-2013 7:45 AM In reply to

      Re: Ambiguity in Namespaces? No way!

      Ronald:
      mikeTheLiar:
      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/

      It's a double quote!

      Nice :D
      Filed under: It's the little things<INPUT id=ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl11_ctl23_ctl01_State value="value:Filed%20under%3A%20%3CA%20href%3D%22%2Ftags%2FIt_2700_s%2Bthe%2Blittle%2Bthings%2Fdefault.aspx%22%20rel%3Dtag%3EIt's%20the%20little%20things%3C%2FA%3E" type=hidden name=ctl00$ctl00$bcr$bcr$ctl00$PostList$ctl11$ctl23$ctl01>
    • 09-26-2013 1:50 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      KattMan:
      NEE!
      Oh, what sad times are these when passing ruffians can say Ni at will to old ladies. There is a pestilence upon this land, nothing is sacred. Even those who arrange and design shrubberies are under considerable economic stress in this period in history.
      TRWTF is people who've never heard of Blinkenlights. The Jargon File should be required reading.
    • 09-26-2013 2:10 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      Did you say shrubberies?
      @blakeyrat said:
      This forum is the worst, and you all are the worst, and mikeTheLiar you're the worst of the worst.
    • 09-26-2013 2:33 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      Yes, shrubberies are my trade. I am a shrubber. My name is Roger the Shrubber. I arrange, design, and sell shrubberies.
      TRWTF is people who've never heard of Blinkenlights. The Jargon File should be required reading.
    • 09-26-2013 2:38 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      PedanticCurmudgeon:
      Yes, shrubberies are my trade. I am a shrubber. My name is Roger the Shrubber. I arrange, design, and sell shrubberies.
      I wish blakeyrat were still around. He hated this sort of thing.
      posted from Excel
    • 09-26-2013 2:48 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      boomzilla:
      PedanticCurmudgeon:
      Yes, shrubberies are my trade. I am a shrubber. My name is Roger the Shrubber. I arrange, design, and sell shrubberies.
      I wish blakeyrat were still around. He hated this sort of thing.
      I wish morbiuswilters were still around. He hated this sort of thing:
      Rosie O'Donnell
      I spend most of my life pressing buttons to make the pattern of lights change however I want.



      Ideas for new messages or themes? PM me.

      Filed under: Randall Munroe does not approve.<INPUT id=ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl16_ctl23_ctl01_State value=value:Filed%20under%3A%20%3CA%20href%3D%22%2Ftags%2FRandall%2BMunroe%2Bdoes%2Bnot%2Bapprove_2E00_%2Fdefault.aspx%22%20rel%3Dtag%3ERandall%20Munroe%20does%20not%20approve.%3C%2FA%3E type=hidden name=ctl00$ctl00$bcr$bcr$ctl00$PostList$ctl16$ctl23$ctl01>
    • 09-26-2013 2:57 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      The scene's over, so you can stop bitching, but are you seriously trying to say that copy/pasting Monty Python is more annoying than blakeyrat?
      TRWTF is people who've never heard of Blinkenlights. The Jargon File should be required reading.
      Filed under: you of all people<INPUT id=ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl17_ctl23_ctl01_State value=value:Filed%20under%3A%20%3CA%20href%3D%22%2Ftags%2Fyou%2Bof%2Ball%2Bpeople%2Fdefault.aspx%22%20rel%3Dtag%3Eyou%20of%20all%20people%3C%2FA%3E type=hidden name=ctl00$ctl00$bcr$bcr$ctl00$PostList$ctl17$ctl23$ctl01>
    • 09-26-2013 2:58 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      PedanticCurmudgeon:
      The scene's over, so you can stop bitching, but are you seriously trying to say that copy/pasting Monty Python is more annoying than blakeyrat?
      I think he's saying that annoying blakeyrat is more amusing than copy/pasting Monty Python.
      I spend most of my life pressing buttons to make the pattern of lights change however I want.



      Ideas for new messages or themes? PM me.

      Filed under: At least I think so.<INPUT id=ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl18_ctl23_ctl01_State value=value:Filed%20under%3A%20%3CA%20href%3D%22%2Ftags%2FAt%2Bleast%2BI%2Bthink%2Bso_2E00_%2Fdefault.aspx%22%20rel%3Dtag%3EAt%20least%20I%20think%20so.%3C%2FA%3E type=hidden name=ctl00$ctl00$bcr$bcr$ctl00$PostList$ctl18$ctl23$ctl01>
    • 09-26-2013 3:02 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      joe.edwards:
      I think he's saying that annoying blakeyrat is more amusing than copy/pasting Monty Python.

      Well, that's true.>

      TRWTF is people who've never heard of Blinkenlights. The Jargon File should be required reading.
    • 09-26-2013 3:42 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      joe.edwards:
      PedanticCurmudgeon:
      The scene's over, so you can stop bitching, but are you seriously trying to say that copy/pasting Monty Python is more annoying than blakeyrat?
      I think he's saying that annoying blakeyrat is more amusing than copy/pasting Monty Python.
      Yes.

       

      And just about anything is more amusing than copy/pasting Monty Python.

      Sent from my phone
    • 09-26-2013 7:54 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      El_Heffe:

      And just about anything is more amusing than copy/pasting Monty Python.

      FTFY.



      Hit Counter


    • 09-26-2013 7:59 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      El_Heffe:
      And just about anything is more amusing than copy/pasting Monty Python.
      That's true. The accents just don't come across, and without the stupid accents it's just not the same. But it's better than posting about video games. Maybe unless it was a Monty Python video game.
      posted from Excel
      Filed under: <FONT color=#698d73>but I'm sure someone will help me out</FONT>, I don't know of any<INPUT id=ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl22_ctl23_ctl01_State value="value:Filed%20under%3A%20%3CA%20href%3D%22%2Ftags%2Fbut%2BI_2700_m%2Bsure%2Bsomeone%2Bwill%2Bhelp%2Bme%2Bout%2Fdefault.aspx%22%20rel%3Dtag%3Ebut%20I'm%20sure%20someone%20will%20help%20me%20out%3C%2FA%3E%2C%20%3CA%20href%3D%22%2Ftags%2FI%2Bdon_2700_t%2Bknow%2Bof%2Bany%2Fdefault.aspx%22%20rel%3Dtag%3EI%20don't%20know%20of%20any%3C%2FA%3E" type=hidden name=ctl00$ctl00$bcr$bcr$ctl00$PostList$ctl22$ctl23$ctl01>
    • 09-26-2013 8:46 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      El_Heffe:
      joe.edwards:
      PedanticCurmudgeon:
      The scene's over, so you can stop bitching, but are you seriously trying to say that copy/pasting Monty Python is more annoying than blakeyrat?
      I think he's saying that annoying blakeyrat is more amusing than copy/pasting Monty Python.
      Yes.

       

      And just about anything is more amusing than copy/pasting Monty Python.

      The set of things blakeyrat is funnier than is a strict superset of the set of things less funny than copy/pasting Monty Python.
      <DF ER>O X>B N BRY UGJTCBI JDABI> DCO OCIBAYGP> >K>PZ RD MF IRE ECE D> HGOY JDABI> DCO OCIBAYGP>Z!
    • 09-26-2013 8:59 PM In reply to

      Just to recap,

      Just to recap,
      <DF ER>O X>B N BRY UGJTCBI JDABI> DCO OCIBAYGP> >K>PZ RD MF IRE ECE D> HGOY JDABI> DCO OCIBAYGP>Z!
      Filed under: Just to recap<INPUT id=ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl24_ctl23_ctl01_State value=value:Filed%20under%3A%20%3CA%20href%3D%22%2Ftags%2FJust%2Bto%2Brecap%2Fdefault.aspx%22%20rel%3Dtag%3EJust%20to%20recap%3C%2FA%3E type=hidden name=ctl00$ctl00$bcr$bcr$ctl00$PostList$ctl24$ctl23$ctl01>
    • 09-26-2013 10:51 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      El_Heffe:
      joe.edwards:
      PedanticCurmudgeon:
      The scene's over, so you can stop bitching, but are you seriously trying to say that copy/pasting Monty Python is more annoying than blakeyrat?
      I think he's saying that annoying blakeyrat is more amusing than copy/pasting Monty Python.
      Yes.

       

      And just about anything is more amusing than copy/pasting Monty Python.

      I think he's pretty funny. I like Fawlty Towers a lot.
    • 09-26-2013 11:02 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
       

       

      Well, I don't know, but I love geometric progressions.

       

    • 09-27-2013 7:17 AM In reply to

      Re: Ambiguity in Namespaces? No way!

      mikeTheLiar:
      Did you say shrubberies?
      I used to be a knight like you, but then I took a shrubbery to the Ni!

       

      Filed under: meme²<INPUT id=ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl27_ctl23_ctl01_State value=value:Filed%20under%3A%20%3CA%20href%3D%22%2Ftags%2Fmeme_26002300_178_3B00_%2Fdefault.aspx%22%20rel%3Dtag%3Ememe%C2%B2%3C%2FA%3E type=hidden name=ctl00$ctl00$bcr$bcr$ctl00$PostList$ctl27$ctl23$ctl01>
    • 09-27-2013 11:32 AM In reply to

      Re: Ambiguity in Namespaces? No way!

      Anonymouse:

       

      mikeTheLiar:
      Did you say shrubberies?
      I used to be a knight like you, but then I took a shrubbery to the Ni!

       

       

       

       

      Feh. Tis but a scratch.

       


      snoofle:We don't have staging servers (they cost money)

    • 09-27-2013 11:40 AM In reply to

      Re: Ambiguity in Namespaces? No way!

      Mcoder:

       

      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
       

       

      Well, I don't know, but I love geometric progressions.

       

      Mcoder:

       

      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
       

       

      Well, I don't know, but I love geometric progressions.

       

      Mcoder:

       

      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
       

       

      Well, I don't know, but I love geometric progressions.

       

       

       

       

      So what happens first-- we discover the value of MAX_POST_SIZE, or a mod gets annoyed?

       


      HardwareGeek:

      <FONT color=#698d73><blink> and you're dead!</FONT>

      <FONT color=#698d73>
      </FONT>
      <FONT color=#698d73>"Where is grumpy cat?"</FONT>
      - Mozilla's MOST ADVANCED USER!
    • 09-27-2013 11:56 AM In reply to

      Re: Ambiguity in Namespaces? No way!

      Lorne Kates:
      Mcoder:

       

      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
       

       

      Well, I don't know, but I love geometric progressions.

       

      Mcoder:

       

      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
       

       

      Well, I don't know, but I love geometric progressions.

       

      Mcoder:

       

      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
       

       

      Well, I don't know, but I love geometric progressions.

       

       

       

       

      So what happens first-- we discover the value of MAX_POST_SIZE, or a mod gets annoyed?

       

      It's probably ntext or nvarchar(max), so I'm betting on the SQL server running out of disk space first.
      I spend most of my life pressing buttons to make the pattern of lights change however I want.



      Ideas for new messages or themes? PM me.

      Filed under: Have you seen the size of the tag cloud hidden field?<INPUT id=ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl30_ctl23_ctl01_State value=value:Filed%20under%3A%20%3CA%20href%3D%22%2Ftags%2FHave%2Byou%2Bseen%2Bthe%2Bsize%2Bof%2Bthe%2Btag%2Bcloud%2Bhidden%2Bfield_3F00_%2Fdefault.aspx%22%20rel%3Dtag%3EHave%20you%20seen%20the%20size%20of%20the%20tag%20cloud%20hidden%20field%3F%3C%2FA%3E type=hidden name=ctl00$ctl00$bcr$bcr$ctl00$PostList$ctl30$ctl23$ctl01>
    Page 1 of 1 (29 items)

    <SCRIPT type=text/javascript> // <!--[CDATA[ Telligent_Modal.Configure('/utility/loading.htm',['CommonModal'],['CommonModalTitle'],['CommonModalClose'],['CommonModalContent'],['CommonModalFooter'],['CommonModalResize'],['CommonModalMask'],100); // ]]--> </SCRIPT> <SCRIPT type=text/javascript> <!-- function KeyDownHandlerctl00_ctl00_bhcr_ctl01_ctl00_TitleBarSearchButton(event) { if (event.keyCode == 13) { event.returnValue = false; event.cancel = true; __doPostBack('ctl00$ctl00$bhcr$ctl01$ctl00$TitleBarSearchButton','') return false; } } //--> </SCRIPT> <SCRIPT type=text/javascript> // <!--[CDATA[ window.ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl02_ctl18_ctl00_ClientPopulatedPopupMenu = new ClientPopulatedPopupMenu('ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl02_ctl18_ctl00_ClientPopulatedPopupMenu','ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl02_ctl18_ctl00','CommonImageTextButton CommonContactButton','CommonImageTextButtonHighlight CommonContactButton',[[new Function('parms', 'return parms[4];'),'View {1}\'s home page','/Themes/leanandgreen/images/common/homepage.gif','{4}','_blank',null],[new Function('parms', 'return parms[5];'),'View {1}\'s weblog','/Themes/leanandgreen/images/common/weblog.gif','{5}','_blank',null],[new Function('parms', 'return parms[6];'),'View {1}\'s gallery','/Themes/leanandgreen/images/common/webgallery.gif','{6}','_blank',null],[new Function('parms', 'return true;'),'View {1}\'s profile','/Themes/leanandgreen/images/common/profile.gif','/user/Profile.aspx?UserID={0}',null,null],[new Function('parms', 'return true;'),'Find posts by {1}','/Themes/leanandgreen/images/common/search.gif','{7}',null,null]]); // ]]--> </SCRIPT> <SCRIPT type=text/javascript> // <!--[CDATA[ window.ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl04_ctl23_ctl01 = new Telligent_InlineEditorPanel('ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl04_ctl23_ctl01','ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl04_ctl23_ctl01','ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl04_ctl23_ctl01_State','ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl04_ctl23_ctl00',false,null,null,null); // ]]--> </SCRIPT> <SCRIPT type=text/javascript> // <!--[CDATA[ window.ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl05_ctl23_ctl01 = new Telligent_InlineEditorPanel('ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl05_ctl23_ctl01','ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl05_ctl23_ctl01','ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl05_ctl23_ctl01_State','ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl04_ctl23_ctl00',false,null,null,null); // ]]--> </SCRIPT> <SCRIPT type=text/javascript> // <!--[CDATA[ window.ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl07_ctl23_ctl01 = new Telligent_InlineEditorPanel('ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl07_ctl23_ctl01','ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl07_ctl23_ctl01','ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl07_ctl23_ctl01_State','ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl04_ctl23_ctl00',false,null,null,null); // ]]--> </SCRIPT> <SCRIPT type=text/javascript> // <!--[CDATA[ window.ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl11_ctl23_ctl01 = new Telligent_InlineEditorPanel('ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl11_ctl23_ctl01','ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl11_ctl23_ctl01','ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl11_ctl23_ctl01_State','ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl04_ctl23_ctl00',false,null,null,null); // ]]--> </SCRIPT> <SCRIPT type=text/javascript> // <!--[CDATA[ window.ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl16_ctl23_ctl01 = new Telligent_InlineEditorPanel('ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl16_ctl23_ctl01','ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl16_ctl23_ctl01','ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl16_ctl23_ctl01_State','ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl04_ctl23_ctl00',false,null,null,null); // ]]--> </SCRIPT> <SCRIPT type=text/javascript> // <!--[CDATA[ window.ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl17_ctl23_ctl01 = new Telligent_InlineEditorPanel('ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl17_ctl23_ctl01','ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl17_ctl23_ctl01','ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl17_ctl23_ctl01_State','ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl04_ctl23_ctl00',false,null,null,null); // ]]--> </SCRIPT> <SCRIPT type=text/javascript> // <!--[CDATA[ window.ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl18_ctl23_ctl01 = new Telligent_InlineEditorPanel('ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl18_ctl23_ctl01','ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl18_ctl23_ctl01','ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl18_ctl23_ctl01_State','ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl04_ctl23_ctl00',false,null,null,null); // ]]--> </SCRIPT> <SCRIPT type=text/javascript> // <!--[CDATA[ window.ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl22_ctl23_ctl01 = new Telligent_InlineEditorPanel('ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl22_ctl23_ctl01','ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl22_ctl23_ctl01','ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl22_ctl23_ctl01_State','ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl04_ctl23_ctl00',false,null,null,null); // ]]--> </SCRIPT> <SCRIPT type=text/javascript> // <!--[CDATA[ window.ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl24_ctl23_ctl01 = new Telligent_InlineEditorPanel('ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl24_ctl23_ctl01','ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl24_ctl23_ctl01','ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl24_ctl23_ctl01_State','ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl04_ctl23_ctl00',false,null,null,null); // ]]--> </SCRIPT> <SCRIPT type=text/javascript> // <!--[CDATA[ window.ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl27_ctl23_ctl01 = new Telligent_InlineEditorPanel('ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl27_ctl23_ctl01','ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl27_ctl23_ctl01','ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl27_ctl23_ctl01_State','ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl04_ctl23_ctl00',false,null,null,null); // ]]--> </SCRIPT> <SCRIPT type=text/javascript> // <!--[CDATA[ window.ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl30_ctl23_ctl01 = new Telligent_InlineEditorPanel('ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl30_ctl23_ctl01','ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl30_ctl23_ctl01','ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl30_ctl23_ctl01_State','ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl04_ctl23_ctl00',false,null,null,null); // ]]--> </SCRIPT> <SCRIPT type=text/javascript> // <!--[CDATA[ window.ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl02_ctl18_ctl00 = new Telligent_PopupMenu('ctl00_ctl00_bcr_bcr_ctl00_PostList_ctl02_ctl18_ctl00','CommonContextMenuGroup','CommonContextMenuItem','CommonContextMenuItemHover','CommonContextMenuItemExpanded','',0,0,20,20,'updown',0,null,null,null,[],false); // ]]--> </SCRIPT> </FORM>



  • @ender said:

    The Daily WTF: Curious Perversions in Information Technology
    in "Side Bar" WTF The Daily WTF (Entire Site) Search

    Ambiguity in Namespaces? No way!

    Last post 09-27-2013 11:56 AM by <font color="#698d73">joe.edwards</font>. 28 replies.
    Page 1 of 1 (29 items)
    Sort Posts: Oldest to newest Newest to oldest Previous Next
    • 09-24-2013 7:36 PM

      Ambiguity in Namespaces? No way!

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      The one, the only true Darsithis™ <font color="#698d73">(Armory)</font> | <font color="#698d73">(Twitter) </font>
      Global Moderator of MMO-Champion.com
    • 09-24-2013 7:52 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      Darsithis:

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.



      Hit Counter


    • 09-24-2013 8:44 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      Ronald:
      Darsithis:

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.
      <DF ER>O X>B N BRY UGJTCBI JDABI> DCO OCIBAYGP> >K>PZ RD MF IRE ECE D> HGOY JDABI> DCO OCIBAYGP>Z!
      Filed under: joke
    • 09-24-2013 9:20 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      Ben L.:
      Ronald:
      Darsithis:

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>



      Hit Counter


      Filed under: Go Fetch
    • 09-24-2013 9:47 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

       

    • 09-25-2013 9:08 AM In reply to

      Re: Ambiguity in Namespaces? No way!

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      This is a signature. It's not a good one, but it's still a signature.






    • <font color="#698d73" size="2"></font>
      <font color="#698d73" size="2"></font>
    • 09-25-2013 9:33 AM In reply to

      Re: Ambiguity in Namespaces? No way!

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
      @blakeyrat said:
      This forum is the worst, and you all are the worst, and mikeTheLiar you're the worst of the worst.
    • 09-25-2013 2:56 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      NEE!
      CAPTCHA? We ain't got no CAPTCHA. We don't need no CAPTCHA. We don't need no stinking CAPTCHA!
    • 09-25-2013 11:13 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      mikeTheLiar:
      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/

      It's a double quote!



      Hit Counter


    • 09-26-2013 7:45 AM In reply to

      Re: Ambiguity in Namespaces? No way!

      Ronald:
      mikeTheLiar:
      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/

      It's a double quote!

      Nice :D
    • 09-26-2013 1:50 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      KattMan:
      NEE!
      Oh, what sad times are these when passing ruffians can say Ni at will to old ladies. There is a pestilence upon this land, nothing is sacred. Even those who arrange and design shrubberies are under considerable economic stress in this period in history.
      TRWTF is people who've never heard of Blinkenlights. The Jargon File should be required reading.
    • 09-26-2013 2:10 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      Did you say shrubberies?
      @blakeyrat said:
      This forum is the worst, and you all are the worst, and mikeTheLiar you're the worst of the worst.
    • 09-26-2013 2:33 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      Yes, shrubberies are my trade. I am a shrubber. My name is Roger the Shrubber. I arrange, design, and sell shrubberies.
      TRWTF is people who've never heard of Blinkenlights. The Jargon File should be required reading.
    • 09-26-2013 2:38 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      PedanticCurmudgeon:
      Yes, shrubberies are my trade. I am a shrubber. My name is Roger the Shrubber. I arrange, design, and sell shrubberies.
      I wish blakeyrat were still around. He hated this sort of thing.
      posted from Excel
    • 09-26-2013 2:48 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      boomzilla:
      PedanticCurmudgeon:
      Yes, shrubberies are my trade. I am a shrubber. My name is Roger the Shrubber. I arrange, design, and sell shrubberies.
      I wish blakeyrat were still around. He hated this sort of thing.
      I wish morbiuswilters were still around. He hated this sort of thing:
      Rosie O'Donnell
      I spend most of my life pressing buttons to make the pattern of lights change however I want.



      Ideas for new messages or themes? PM me.

    • 09-26-2013 2:57 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      The scene's over, so you can stop bitching, but are you seriously trying to say that copy/pasting Monty Python is more annoying than blakeyrat?
      TRWTF is people who've never heard of Blinkenlights. The Jargon File should be required reading.
      Filed under: you of all people
    • 09-26-2013 2:58 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      PedanticCurmudgeon:
      The scene's over, so you can stop bitching, but are you seriously trying to say that copy/pasting Monty Python is more annoying than blakeyrat?
      I think he's saying that annoying blakeyrat is more amusing than copy/pasting Monty Python.
      I spend most of my life pressing buttons to make the pattern of lights change however I want.



      Ideas for new messages or themes? PM me.

    • 09-26-2013 3:02 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      joe.edwards:
      I think he's saying that annoying blakeyrat is more amusing than copy/pasting Monty Python.

      Well, that's true.>

      TRWTF is people who've never heard of Blinkenlights. The Jargon File should be required reading.
    • 09-26-2013 3:42 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      joe.edwards:
      PedanticCurmudgeon:
      The scene's over, so you can stop bitching, but are you seriously trying to say that copy/pasting Monty Python is more annoying than blakeyrat?
      I think he's saying that annoying blakeyrat is more amusing than copy/pasting Monty Python.
      Yes.

       

      And just about anything is more amusing than copy/pasting Monty Python.

      Sent from my phone
    • 09-26-2013 7:54 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      El_Heffe:

      And just about anything is more amusing than copy/pasting Monty Python.

      FTFY.



      Hit Counter


    • 09-26-2013 7:59 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      El_Heffe:
      And just about anything is more amusing than copy/pasting Monty Python.
      That's true. The accents just don't come across, and without the stupid accents it's just not the same. But it's better than posting about video games. Maybe unless it was a Monty Python video game.
      posted from Excel
    • 09-26-2013 8:46 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      El_Heffe:
      joe.edwards:
      PedanticCurmudgeon:
      The scene's over, so you can stop bitching, but are you seriously trying to say that copy/pasting Monty Python is more annoying than blakeyrat?
      I think he's saying that annoying blakeyrat is more amusing than copy/pasting Monty Python.
      Yes.

       

      And just about anything is more amusing than copy/pasting Monty Python.

      The set of things blakeyrat is funnier than is a strict superset of the set of things less funny than copy/pasting Monty Python.
      <DF ER>O X>B N BRY UGJTCBI JDABI> DCO OCIBAYGP> >K>PZ RD MF IRE ECE D> HGOY JDABI> DCO OCIBAYGP>Z!
    • 09-26-2013 8:59 PM In reply to

      Just to recap,

      Just to recap,
      <DF ER>O X>B N BRY UGJTCBI JDABI> DCO OCIBAYGP> >K>PZ RD MF IRE ECE D> HGOY JDABI> DCO OCIBAYGP>Z!
      Filed under: Just to recap
    • 09-26-2013 10:51 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      El_Heffe:
      joe.edwards:
      PedanticCurmudgeon:
      The scene's over, so you can stop bitching, but are you seriously trying to say that copy/pasting Monty Python is more annoying than blakeyrat?
      I think he's saying that annoying blakeyrat is more amusing than copy/pasting Monty Python.
      Yes.

       

      And just about anything is more amusing than copy/pasting Monty Python.

      I think he's pretty funny. I like Fawlty Towers a lot.
    • 09-26-2013 11:02 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
       

       

      Well, I don't know, but I love geometric progressions.

       

    • 09-27-2013 7:17 AM In reply to

      Re: Ambiguity in Namespaces? No way!

      mikeTheLiar:
      Did you say shrubberies?
      I used to be a knight like you, but then I took a shrubbery to the Ni!

       

      Filed under: meme²
    • 09-27-2013 11:32 AM In reply to

      Re: Ambiguity in Namespaces? No way!

      Anonymouse:

       

      mikeTheLiar:
      Did you say shrubberies?
      I used to be a knight like you, but then I took a shrubbery to the Ni!

       

       

       

       

      Feh. Tis but a scratch.

       


      snoofle:We don't have staging servers (they cost money)

    • 09-27-2013 11:40 AM In reply to

      Re: Ambiguity in Namespaces? No way!

      Mcoder:

       

      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
       

       

      Well, I don't know, but I love geometric progressions.

       

      Mcoder:

       

      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
       

       

      Well, I don't know, but I love geometric progressions.

       

      Mcoder:

       

      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
       

       

      Well, I don't know, but I love geometric progressions.

       

       

       

       

      So what happens first-- we discover the value of MAX_POST_SIZE, or a mod gets annoyed?

       


      HardwareGeek:

      <font color="#698d73"><blink> and you're dead!</font>

      <font color="#698d73">
      </font>
      <font color="#698d73">"Where is grumpy cat?"</font>
      - Mozilla's MOST ADVANCED USER!
    • 09-27-2013 11:56 AM In reply to

      Re: Ambiguity in Namespaces? No way!

      Lorne Kates:
      Mcoder:

       

      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
       

       

      Well, I don't know, but I love geometric progressions.

       

      Mcoder:

       

      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
       

       

      Well, I don't know, but I love geometric progressions.

       

      Mcoder:

       

      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
       

       

      Well, I don't know, but I love geometric progressions.

       

       

       

       

      So what happens first-- we discover the value of MAX_POST_SIZE, or a mod gets annoyed?

       

      It's probably ntext or nvarchar(max), so I'm betting on the SQL server running out of disk space first.
      I spend most of my life pressing buttons to make the pattern of lights change however I want.



      Ideas for new messages or themes? PM me.

    Page 1 of 1 (29 items)

    //

    //

    //

    //

    //

    //

    //

    //

    //

    //

    //

    //

    //

    //

    You win +1 internet, sir.


  •  [Message clipped]  View entire message



  • @Lorne Kates said:

     [Message clipped]  View entire message

    HOW DID YOU HACK IN MY GMAIL ACCOUNT YOU DEVIL

    dear sir please give teh code to do it



  • @Ronald said:

    HOW DID YOU HACK IN MY GMAIL ACCOUNT YOU DEVIL

    dear sir please give teh code to do it

     

    step 1: go to gmail.com

    step 2: enter usernaem and password of person account you hack wish

    step 3: hack by pressing sign in

     



  • @Lorne Kates said:

    @Ronald said:

    HOW DID YOU HACK IN MY GMAIL ACCOUNT YOU DEVIL

    dear sir please give teh code to do it

     

    step 1: go to gmail.com

    step 2: enter usernaem and password of person account you hack wish

    step 3: hack by pressing sign in

     

    OH GOD IT WORKS

    SOMEONE FILE A VULNERABILITY REPORT



  • @Ben L. said:

    @Lorne Kates said:

    @Ronald said:

    HOW DID YOU HACK IN MY GMAIL ACCOUNT YOU DEVIL

    dear sir please give teh code to do it

     

    step 1: go to gmail.com

    step 2: enter usernaem and password of person account you hack wish

    step 3: hack by pressing sign in

     

    OH GOD IT WORKS

    SOMEONE FILE A ZERO-DAY VULNERABILITY REPORT

    FTFY. As far as I know this has never been patched but Google is doing their best to make the exploit extremely annoying, especially if you travel a lot.



  • @mikeTheLiar said:

    @ender said:

     

    The Daily WTF: Curious Perversions in Information Technology
    in "Side Bar" WTF The Daily WTF (Entire Site) Search

     

    Ambiguity in Namespaces? No way!

    Last post 09-27-2013 11:56 AM by <font color="#698d73">joe.edwards</font>. 28 replies.
    Page 1 of 1 (29 items)
    Sort Posts: Oldest to newest Newest to oldest Previous Next
    • 09-24-2013 7:36 PM

      Ambiguity in Namespaces? No way!

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      The one, the only true Darsithis™ <font color="#698d73">(Armory)</font> | <font color="#698d73">(Twitter) </font>
      Global Moderator of MMO-Champion.com
    • 09-24-2013 7:52 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      Darsithis:

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.



      Hit Counter


    • 09-24-2013 8:44 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      Ronald:
      Darsithis:

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.
      <DF ER>O X>B N BRY UGJTCBI JDABI> DCO OCIBAYGP> >K>PZ RD MF IRE ECE D> HGOY JDABI> DCO OCIBAYGP>Z!
      Filed under: joke
    • 09-24-2013 9:20 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      Ben L.:
      Ronald:
      Darsithis:

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>



      Hit Counter


      Filed under: Go Fetch
    • 09-24-2013 9:47 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

       

    • 09-25-2013 9:08 AM In reply to

      Re: Ambiguity in Namespaces? No way!

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      This is a signature. It's not a good one, but it's still a signature.






    • <font color="#698d73" size="2"></font>
      <font color="#698d73" size="2"></font>
    • 09-25-2013 9:33 AM In reply to

      Re: Ambiguity in Namespaces? No way!

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
      @blakeyrat said:
      This forum is the worst, and you all are the worst, and mikeTheLiar you're the worst of the worst.
    • 09-25-2013 2:56 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      NEE!
      CAPTCHA? We ain't got no CAPTCHA. We don't need no CAPTCHA. We don't need no stinking CAPTCHA!
    • 09-25-2013 11:13 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      mikeTheLiar:
      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/

      It's a double quote!



      Hit Counter


    • 09-26-2013 7:45 AM In reply to

      Re: Ambiguity in Namespaces? No way!

      Ronald:
      mikeTheLiar:
      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/

      It's a double quote!

      Nice :D
    • 09-26-2013 1:50 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      KattMan:
      NEE!
      Oh, what sad times are these when passing ruffians can say Ni at will to old ladies. There is a pestilence upon this land, nothing is sacred. Even those who arrange and design shrubberies are under considerable economic stress in this period in history.
      TRWTF is people who've never heard of Blinkenlights. The Jargon File should be required reading.
    • 09-26-2013 2:10 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      Did you say shrubberies?
      @blakeyrat said:
      This forum is the worst, and you all are the worst, and mikeTheLiar you're the worst of the worst.
    • 09-26-2013 2:33 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      Yes, shrubberies are my trade. I am a shrubber. My name is Roger the Shrubber. I arrange, design, and sell shrubberies.
      TRWTF is people who've never heard of Blinkenlights. The Jargon File should be required reading.
    • 09-26-2013 2:38 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      PedanticCurmudgeon:
      Yes, shrubberies are my trade. I am a shrubber. My name is Roger the Shrubber. I arrange, design, and sell shrubberies.
      I wish blakeyrat were still around. He hated this sort of thing.
      posted from Excel
    • 09-26-2013 2:48 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      boomzilla:
      PedanticCurmudgeon:
      Yes, shrubberies are my trade. I am a shrubber. My name is Roger the Shrubber. I arrange, design, and sell shrubberies.
      I wish blakeyrat were still around. He hated this sort of thing.
      I wish morbiuswilters were still around. He hated this sort of thing:
      Rosie O'Donnell
      I spend most of my life pressing buttons to make the pattern of lights change however I want.



      Ideas for new messages or themes? PM me.

    • 09-26-2013 2:57 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      The scene's over, so you can stop bitching, but are you seriously trying to say that copy/pasting Monty Python is more annoying than blakeyrat?
      TRWTF is people who've never heard of Blinkenlights. The Jargon File should be required reading.
      Filed under: you of all people
    • 09-26-2013 2:58 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      PedanticCurmudgeon:
      The scene's over, so you can stop bitching, but are you seriously trying to say that copy/pasting Monty Python is more annoying than blakeyrat?
      I think he's saying that annoying blakeyrat is more amusing than copy/pasting Monty Python.
      I spend most of my life pressing buttons to make the pattern of lights change however I want.



      Ideas for new messages or themes? PM me.

    • 09-26-2013 3:02 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      joe.edwards:
      I think he's saying that annoying blakeyrat is more amusing than copy/pasting Monty Python.

      Well, that's true.>

      TRWTF is people who've never heard of Blinkenlights. The Jargon File should be required reading.
    • 09-26-2013 3:42 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      joe.edwards:
      PedanticCurmudgeon:
      The scene's over, so you can stop bitching, but are you seriously trying to say that copy/pasting Monty Python is more annoying than blakeyrat?
      I think he's saying that annoying blakeyrat is more amusing than copy/pasting Monty Python.
      Yes.

       

      And just about anything is more amusing than copy/pasting Monty Python.

      Sent from my phone
    • 09-26-2013 7:54 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      El_Heffe:

      And just about anything is more amusing than copy/pasting Monty Python.

      FTFY.



      Hit Counter


    • 09-26-2013 7:59 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      El_Heffe:
      And just about anything is more amusing than copy/pasting Monty Python.
      That's true. The accents just don't come across, and without the stupid accents it's just not the same. But it's better than posting about video games. Maybe unless it was a Monty Python video game.
      posted from Excel
    • 09-26-2013 8:46 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      El_Heffe:
      joe.edwards:
      PedanticCurmudgeon:
      The scene's over, so you can stop bitching, but are you seriously trying to say that copy/pasting Monty Python is more annoying than blakeyrat?
      I think he's saying that annoying blakeyrat is more amusing than copy/pasting Monty Python.
      Yes.

       

      And just about anything is more amusing than copy/pasting Monty Python.

      The set of things blakeyrat is funnier than is a strict superset of the set of things less funny than copy/pasting Monty Python.
      <DF ER>O X>B N BRY UGJTCBI JDABI> DCO OCIBAYGP> >K>PZ RD MF IRE ECE D> HGOY JDABI> DCO OCIBAYGP>Z!
    • 09-26-2013 8:59 PM In reply to

      Just to recap,

      Just to recap,
      <DF ER>O X>B N BRY UGJTCBI JDABI> DCO OCIBAYGP> >K>PZ RD MF IRE ECE D> HGOY JDABI> DCO OCIBAYGP>Z!
      Filed under: Just to recap
    • 09-26-2013 10:51 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      El_Heffe:
      joe.edwards:
      PedanticCurmudgeon:
      The scene's over, so you can stop bitching, but are you seriously trying to say that copy/pasting Monty Python is more annoying than blakeyrat?
      I think he's saying that annoying blakeyrat is more amusing than copy/pasting Monty Python.
      Yes.

       

      And just about anything is more amusing than copy/pasting Monty Python.

      I think he's pretty funny. I like Fawlty Towers a lot.
    • 09-26-2013 11:02 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
       

       

      Well, I don't know, but I love geometric progressions.

       

    • 09-27-2013 7:17 AM In reply to

      Re: Ambiguity in Namespaces? No way!

      mikeTheLiar:
      Did you say shrubberies?
      I used to be a knight like you, but then I took a shrubbery to the Ni!

       

      Filed under: meme²
    • 09-27-2013 11:32 AM In reply to

      Re: Ambiguity in Namespaces? No way!

      Anonymouse:

       

      mikeTheLiar:
      Did you say shrubberies?
      I used to be a knight like you, but then I took a shrubbery to the Ni!

       

       

       

       

      Feh. Tis but a scratch.

       


      snoofle:We don't have staging servers (they cost money)

    • 09-27-2013 11:40 AM In reply to

      Re: Ambiguity in Namespaces? No way!

      Mcoder:

       

      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
       

       

      Well, I don't know, but I love geometric progressions.

       

      Mcoder:

       

      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
       

       

      Well, I don't know, but I love geometric progressions.

       

      Mcoder:

       

      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
       

       

      Well, I don't know, but I love geometric progressions.

       

       

       

       

      So what happens first-- we discover the value of MAX_POST_SIZE, or a mod gets annoyed?

       


      HardwareGeek:

      <font color="#698d73"><blink> and you're dead!</font>

      <font color="#698d73">
      </font>
      <font color="#698d73">"Where is grumpy cat?"</font>
      - Mozilla's MOST ADVANCED USER!
    • 09-27-2013 11:56 AM In reply to

      Re: Ambiguity in Namespaces? No way!

      Lorne Kates:
      Mcoder:

       

      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
       

       

      Well, I don't know, but I love geometric progressions.

       

      Mcoder:

       

      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
       

       

      Well, I don't know, but I love geometric progressions.

       

      Mcoder:

       

      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <font color="#698d73">There you go!</font>

      <font color="#698d73"></font>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
       

       

      Well, I don't know, but I love geometric progressions.

       

       

       

       

      So what happens first-- we discover the value of MAX_POST_SIZE, or a mod gets annoyed?

       

      It's probably ntext or nvarchar(max), so I'm betting on the SQL server running out of disk space first.
      I spend most of my life pressing buttons to make the pattern of lights change however I want.



      Ideas for new messages or themes? PM me.

    Page 1 of 1 (29 items)

    //

    //

    //

    //

    //

    //

    //

    //

    //

    //

    //

    //

    //

    //

    You win +1 internet, sir.
     

    I really want to turn this into a sig hack, but the truth is I'm not that bored yet.

     



  • The Daily WTF: Curious Perversions in Information Technology
    <INPUT onblur="if(this.value=='') this.value=this.defaultValue;" onkeydown="return KeyDownHandlerctl00_ctl00_bhcr_ctl01_ctl00_TitleBarSearchButton(event);" id=ctl00_ctl00_bhcr_ctl01_ctl00_TitleBarSearchText onclick="if(this.defaultValue==this.value) this.value='';" maxLength=64 size=15 name=ctl00$ctl00$bhcr$ctl01$ctl00$TitleBarSearchText> in <SELECT id=ctl00_ctl00_bhcr_ctl01_ctl00_ctl00_ctl02_TitleBarSearchDropDownList name=ctl00$ctl00$bhcr$ctl01$ctl00$ctl00$ctl02$TitleBarSearchDropDownList> <OPTION selected value=S:18>"Side Bar" WTF</OPTION> <OPTION value=G:4>The Daily WTF</OPTION> <OPTION value=:>(Entire Site)</OPTION></SELECT> Search

    <SCRIPT type=text/javascript> // <!--[CDATA[ function tabOver(e) { if (e.className!='CommonSimpleTabStripSelectedTab') e.className='CommonSimpleTabStripTabHover'; } function tabOut(e) { if (e.className!='CommonSimpleTabStripSelectedTab') e.className='CommonSimpleTabStripTab'; } // ]]--> </SCRIPT>
    <SCRIPT type=text/javascript> // <!--[CDATA[ function ToggleInk(cb) { if(cb.checked) document.getElementById('inkWrapper').style.position= 'static'; else document.getElementById('inkWrapper').style.position= 'absolute'; } function InkHidden() { InkCheck(false); } function InkVisible() { InkCheck(true); } function InkCheck(showInk) { var inkCheckCB = document.getElementById('ctl00_ctl00_bcr_bcr_PostForm_ctl04_InkSubForm_ctl00_EnableInk'); var inkCheckInkEditor = document.getElementById('inkWrapper'); if(showInk && inkCheckCB && inkCheckCB.checked) inkCheckInkEditor.style.position= 'static'; else inkCheckInkEditor.style.position= 'absolute'; <pre--> return true; }

    // ]]>
    </SCRIPT>

    Reply to an Existing Message

    The message you are replying to: Re: Ambiguity in Namespaces? No way!
    Compose
    Options
    Related
    Preview
    mott555 wrote the following post at 27 Sep 2013 9:31 PM:

    @mikeTheLiar said:

    @ender said:

     

    The Daily WTF: Curious Perversions in Information Technology
    in "Side Bar" WTF The Daily WTF (Entire Site) Search

     

    Ambiguity in Namespaces? No way!

    Last post 09-27-2013 11:56 AM by <FONT color=#698d73>joe.edwards</FONT>. 28 replies.
    Page 1 of 1 (29 items)
    Sort Posts: Oldest to newest Newest to oldest Previous Next
    • 09-24-2013 7:36 PM

      Ambiguity in Namespaces? No way!

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      The one, the only true Darsithis™ <FONT color=#698d73>(Armory)</FONT> | <FONT color=#698d73>(Twitter) </FONT>
      Global Moderator of MMO-Champion.com
    • 09-24-2013 7:52 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      Darsithis:

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.



      Hit Counter


    • 09-24-2013 8:44 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      Ronald:
      Darsithis:

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.
      <DF ER>O X>B N BRY UGJTCBI JDABI> DCO OCIBAYGP> >K>PZ RD MF IRE ECE D> HGOY JDABI> DCO OCIBAYGP>Z!
      • <FONT color=#698d73></FONT>
    • <FONT color=#698d73></FONT> 09-24-2013 9:20 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      Ben L.:
      Ronald:
      Darsithis:

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>



      Hit Counter


      • <FONT color=#698d73></FONT>
    • <FONT color=#698d73></FONT> 09-24-2013 9:47 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

       

    • 09-25-2013 9:08 AM In reply to

      Re: Ambiguity in Namespaces? No way!

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      This is a signature. It's not a good one, but it's still a signature.


    • <FONT color=#698d73 size=2></FONT> Mon, February 30 2010 2:64 PM



      I have cornified this thread, pray I don't cornify it further.






    • <FONT color=#698d73 size=2></FONT>
      <FONT color=#698d73 size=2></FONT>
      • <FONT color=#698d73></FONT>
    • <FONT color=#698d73></FONT> 09-25-2013 9:33 AM In reply to

      Re: Ambiguity in Namespaces? No way!

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
      @blakeyrat said:
      This forum is the worst, and you all are the worst, and mikeTheLiar you're the worst of the worst.
    • 09-25-2013 2:56 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      NEE!
      CAPTCHA? We ain't got no CAPTCHA. We don't need no CAPTCHA. We don't need no stinking CAPTCHA!
    • 09-25-2013 11:13 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      mikeTheLiar:
      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/

      It's a double quote!



      Hit Counter


    • 09-26-2013 7:45 AM In reply to

      Re: Ambiguity in Namespaces? No way!

      Ronald:
      mikeTheLiar:
      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/

      It's a double quote!

      Nice :D
      • <FONT color=#698d73></FONT>
    • <FONT color=#698d73></FONT> 09-26-2013 1:50 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      KattMan:
      NEE!
      Oh, what sad times are these when passing ruffians can say Ni at will to old ladies. There is a pestilence upon this land, nothing is sacred. Even those who arrange and design shrubberies are under considerable economic stress in this period in history.
      TRWTF is people who've never heard of Blinkenlights. The Jargon File should be required reading.
    • 09-26-2013 2:10 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      Did you say shrubberies?
      @blakeyrat said:
      This forum is the worst, and you all are the worst, and mikeTheLiar you're the worst of the worst.
    • 09-26-2013 2:33 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      Yes, shrubberies are my trade. I am a shrubber. My name is Roger the Shrubber. I arrange, design, and sell shrubberies.
      TRWTF is people who've never heard of Blinkenlights. The Jargon File should be required reading.
    • 09-26-2013 2:38 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      PedanticCurmudgeon:
      Yes, shrubberies are my trade. I am a shrubber. My name is Roger the Shrubber. I arrange, design, and sell shrubberies.
      I wish blakeyrat were still around. He hated this sort of thing.
      posted from Excel
    • 09-26-2013 2:48 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      boomzilla:
      PedanticCurmudgeon:
      Yes, shrubberies are my trade. I am a shrubber. My name is Roger the Shrubber. I arrange, design, and sell shrubberies.
      I wish blakeyrat were still around. He hated this sort of thing.
      I wish morbiuswilters were still around. He hated this sort of thing:
      Rosie O'Donnell
      I spend most of my life pressing buttons to make the pattern of lights change however I want.



      Ideas for new messages or themes? PM me.

      • <FONT color=#698d73></FONT>
    • <FONT color=#698d73></FONT> 09-26-2013 2:57 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      The scene's over, so you can stop bitching, but are you seriously trying to say that copy/pasting Monty Python is more annoying than blakeyrat?
      TRWTF is people who've never heard of Blinkenlights. The Jargon File should be required reading.
      • <FONT color=#698d73></FONT>
    • <FONT color=#698d73></FONT> 09-26-2013 2:58 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      PedanticCurmudgeon:
      The scene's over, so you can stop bitching, but are you seriously trying to say that copy/pasting Monty Python is more annoying than blakeyrat?
      I think he's saying that annoying blakeyrat is more amusing than copy/pasting Monty Python.
      I spend most of my life pressing buttons to make the pattern of lights change however I want.



      Ideas for new messages or themes? PM me.

      • <FONT color=#698d73></FONT>
    • <FONT color=#698d73></FONT> 09-26-2013 3:02 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      joe.edwards:
      I think he's saying that annoying blakeyrat is more amusing than copy/pasting Monty Python.

      Well, that's true.>

      TRWTF is people who've never heard of Blinkenlights. The Jargon File should be required reading.
    • 09-26-2013 3:42 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      joe.edwards:
      PedanticCurmudgeon:
      The scene's over, so you can stop bitching, but are you seriously trying to say that copy/pasting Monty Python is more annoying than blakeyrat?
      I think he's saying that annoying blakeyrat is more amusing than copy/pasting Monty Python.
      Yes.

       

      And just about anything is more amusing than copy/pasting Monty Python.

      Sent from my phone
    • 09-26-2013 7:54 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      El_Heffe:

      And just about anything is more amusing than copy/pasting Monty Python.

      FTFY.



      Hit Counter


    • 09-26-2013 7:59 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      El_Heffe:
      And just about anything is more amusing than copy/pasting Monty Python.
      That's true. The accents just don't come across, and without the stupid accents it's just not the same. But it's better than posting about video games. Maybe unless it was a Monty Python video game.
      posted from Excel
      • <FONT color=#698d73></FONT>
    • <FONT color=#698d73></FONT> 09-26-2013 8:46 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      El_Heffe:
      joe.edwards:
      PedanticCurmudgeon:
      The scene's over, so you can stop bitching, but are you seriously trying to say that copy/pasting Monty Python is more annoying than blakeyrat?
      I think he's saying that annoying blakeyrat is more amusing than copy/pasting Monty Python.
      Yes.

       

      And just about anything is more amusing than copy/pasting Monty Python.

      The set of things blakeyrat is funnier than is a strict superset of the set of things less funny than copy/pasting Monty Python.
      <DF ER>O X>B N BRY UGJTCBI JDABI> DCO OCIBAYGP> >K>PZ RD MF IRE ECE D> HGOY JDABI> DCO OCIBAYGP>Z!
    • 09-26-2013 8:59 PM In reply to

      Just to recap,

      Just to recap,
      <DF ER>O X>B N BRY UGJTCBI JDABI> DCO OCIBAYGP> >K>PZ RD MF IRE ECE D> HGOY JDABI> DCO OCIBAYGP>Z!
      • <FONT color=#698d73></FONT>
    • <FONT color=#698d73></FONT> 09-26-2013 10:51 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      El_Heffe:
      joe.edwards:
      PedanticCurmudgeon:
      The scene's over, so you can stop bitching, but are you seriously trying to say that copy/pasting Monty Python is more annoying than blakeyrat?
      I think he's saying that annoying blakeyrat is more amusing than copy/pasting Monty Python.
      Yes.

       

      And just about anything is more amusing than copy/pasting Monty Python.

      I think he's pretty funny. I like Fawlty Towers a lot.
    • 09-26-2013 11:02 PM In reply to

      Re: Ambiguity in Namespaces? No way!

      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
       

       

      Well, I don't know, but I love geometric progressions.

       

    • 09-27-2013 7:17 AM In reply to

      Re: Ambiguity in Namespaces? No way!

      mikeTheLiar:
      Did you say shrubberies?
      I used to be a knight like you, but then I took a shrubbery to the Ni!

       

      • <FONT color=#698d73></FONT>
    • <FONT color=#698d73></FONT> 09-27-2013 11:32 AM In reply to

      Re: Ambiguity in Namespaces? No way!

      Anonymouse:

       

      mikeTheLiar:
      Did you say shrubberies?
      I used to be a knight like you, but then I took a shrubbery to the Ni!

       

       

       

       

      Feh. Tis but a scratch.

       


      snoofle:We don't have staging servers (they cost money)

    • 09-27-2013 11:40 AM In reply to

      Re: Ambiguity in Namespaces? No way!

      Mcoder:

       

      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
       

       

      Well, I don't know, but I love geometric progressions.

       

      Mcoder:

       

      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
       

       

      Well, I don't know, but I love geometric progressions.

       

      Mcoder:

       

      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
       

       

      Well, I don't know, but I love geometric progressions.

       

       

       

       

      So what happens first-- we discover the value of MAX_POST_SIZE, or a mod gets annoyed?

       


      HardwareGeek:

      <FONT color=#698d73><blink> and you're dead!</FONT>

      <FONT color=#698d73>
      </FONT>
      <FONT color=#698d73>"Where is grumpy cat?"</FONT>
      - Mozilla's MOST ADVANCED USER!
    • 09-27-2013 11:56 AM In reply to

      Re: Ambiguity in Namespaces? No way!

      Lorne Kates:
      Mcoder:

       

      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
       

       

      Well, I don't know, but I love geometric progressions.

       

      Mcoder:

       

      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
       

       

      Well, I don't know, but I love geometric progressions.

       

      Mcoder:

       

      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
      mikeTheLiar:
      mott555:

       

      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

      mott555:
      Mcoder:

       

      Ronald:
      Ben L.:
      Ronald:
      Darsithis:

       

      So lately I’ve been getting this error message on a lot of pages in this project in the compiled, published version only:

      BC30456: 'Title' is not a member of xxxx page

      Was driving me nuts. I tried all of the possible fixes: I rebuilt the solution and cleaned it. I deleted the entire site from the publish location so I was sure it was fresh. Nothing worked. Finally I saw what the issue was…

      …that idiot overseas developer that was hired to work on this decided to take a shortcut. He copied all of the Time Card report pages into Work Center without changing the class they inherit from in the markup. That means instead of inheriting from WorkCenter_Reports_XXXXXX, they’d inherit from TC_Reports_XXXXX and most of them had the same name!

      So the compiled version of the site was seeing two sets of reports in two places, and that was causing an issue with ambiguity. I want to tear my hair out!

      I've often seen a similar error message when trying to use resources files (string tables) to set the title in a Master Page. That happens mostly when working on themed or multilingual sites.

      ASP.Net Web forms make it very easy to do that kind of thing (global/local resources cascade, locale-specific extensions, etc.) but as usual the Master Pages are sand in the gears.

      You shouldn't quote the entire OP.

      <FONT color=#698d73>There you go!</FONT>

      <FONT color=#698d73></FONT>

       

       

      Now, you two!  Stop quoting the entire OP!

      Stop saying it! Oh know, now I've said it! We're all saying it! Aaahh!!

       

       

       

      FUCKING HELL WHY DOES IT QUOTE TWICE WHEN I PRESS QUOTE ONCE?!?!?!?/
       

       

      Well, I don't know, but I love geometric progressions.

       

       

       

       

      So what happens first-- we discover the value of MAX_POST_SIZE, or a mod gets annoyed?

       

      It's probably ntext or nvarchar(max), so I'm betting on the SQL server running out of disk space first.
      I spend most of my life pressing buttons to make the pattern of lights change however I want.



      Ideas for new messages or themes? PM me.

      • <FONT color=#698d73></FONT>
    Page 1 of 1 (29 items)

    // // // // // // // // // // // // // //

    You win +1 internet, sir.
     

    I really want to turn this into a sig hack, but the truth is I'm not that bored yet.

     

    Quote
    <LABEL id=ctl00_ctl00_bcr_bcr_PostForm_ctl04_ctl04_ctl00 for=ctl00_ctl00_bcr_bcr_PostForm_ctl04_PostSubject>Subject</LABEL> *
    <INPUT style="WIDTH: 80%" id=ctl00_ctl00_bcr_bcr_PostForm_ctl04_PostSubject class=CommonInputBig value="Re: Ambiguity in Namespaces? No way!" name=ctl00$ctl00$bcr$bcr$PostForm$ctl04$PostSubject autocomplete="off">
    <LABEL id=ctl00_ctl00_bcr_bcr_PostForm_ctl04_ctl05_ctl00 for=ctl00_ctl00_bcr_bcr_PostForm_ctl04_PostBody>Message</LABEL>    
    <SELECT id=mce_editor_0_fontNameSelect class=mceSelectList onfocus="tinyMCE.addSelectAccessibility(event, this, window);" tabIndex=-1 onchange="tinyMCE.execInstanceCommand('mce_editor_0','FontName',false,this.options[this.selectedIndex].value);" name=mce_editor_0_fontNameSelect><OPTION selected value="">-- Font family --</OPTION><OPTION value="andale mono,times">Andale Mono</OPTION><OPTION value=arial,helvetica,sans-serif>Arial</OPTION><OPTION value="arial black,avant garde">Arial Black</OPTION><OPTION value="book antiqua,palatino">Book Antiqua</OPTION><OPTION value="comic sans ms,sand">Comic Sans MS</OPTION><OPTION value="courier new,courier">Courier New</OPTION><OPTION value=georgia,palatino>Georgia</OPTION><OPTION value=helvetica>Helvetica</OPTION><OPTION value=impact,chicago>Impact</OPTION><OPTION value=symbol>Symbol</OPTION><OPTION value=tahoma,arial,helvetica,sans-serif>Tahoma</OPTION><OPTION value=terminal,monaco>Terminal</OPTION><OPTION value="times new roman,times">Times New Roman</OPTION><OPTION value="trebuchet ms,geneva">Trebuchet MS</OPTION><OPTION value=verdana,geneva>Verdana</OPTION><OPTION value=webdings>Webdings</OPTION><OPTION value="wingdings,zapf dingbats">Wingdings</OPTION></SELECT><SELECT id=mce_editor_0_fontSizeSelect class=mceSelectList onfocus="tinyMCE.addSelectAccessibility(event, this, window);" tabIndex=-1 onchange="tinyMCE.execInstanceCommand('mce_editor_0','FontSize',false,this.options[this.selectedIndex].value);" name=mce_editor_0_fontSizeSelect><OPTION selected value=0>-- Font size --</OPTION><OPTION value=1>1 (8 pt)</OPTION><OPTION value=2>2 (10 pt)</OPTION><OPTION value=3>3 (12 pt)</OPTION><OPTION value=4>4 (14 pt)</OPTION><OPTION value=5>5 (18 pt)</OPTION><OPTION value=6>6 (24 pt)</OPTION><OPTION value=7>7 (36 pt)</OPTION></SELECT>CutCopyPastePaste from WordEdit HTML SourceRun spell checking
    Bold (Ctrl+B)Italic (Ctrl+I)Underline (Ctrl+U)StrikethroughIndentOutdentUnordered listOrdered listInsert/edit linkUnlinkInsert/edit image
    <IFRAME style="WIDTH: 100%; HEIGHT: 227px" id=mce_editor_0 class=mceEditorIframe height=227 marginHeight=0 border=0 src="http://forums.thedailywtf.com/tiny_mce/jscripts/tiny_mce/blank.htm" frameBorder=0 width="100%" allowTransparency name=mce_editor_0 marginWidth=0 leftMargin="0" topMargin="0"></IFRAME>
    Path: p 

    <TEXTAREA style="WIDTH: 100%; DISPLAY: none; HEIGHT: 290px" id=ctl00_ctl00_bcr_bcr_PostForm_ctl04_PostBody_ctl00_Editor name=ctl00$ctl00$bcr$bcr$PostForm$ctl04$PostBody$ctl00$Editor><P>&nbsp;</P></TEXTAREA> <SCRIPT language=javascript type=text/javascript src="/tiny_mce/jscripts/tiny_mce/tiny_mce_gzip.js"></SCRIPT> <SCRIPT language=javascript type=text/javascript> // <!--[CDATA[ tinyMCE_GZ.init({disk_cache:false,debug:false,themes:'advanced',plugins:'contentselector,paste,smilies,iespell'}); // ]]--> </SCRIPT> <SCRIPT type=text/javascript>eval(tinyMCE_GZ.scriptData);</SCRIPT> <SCRIPT language=javascript type=text/javascript> // <!--[CDATA[ tinyMCE_CommunityServerOptions = {ContentSelectorOpenFunction:new Function("window.ContentSelectorCallbackFunction = new Function('content', 'TinyMCE_ContentSelectorPlugin._addContent(content);');; Telligent_Modal.Open('/utility/ContentSelector.aspx', 600, 420, null);"),Smilies:[],GetBaseUrl:new Function("try { if (window.parent && window.parent.Telligent_Modal) return window.parent.location + \"\"; } catch (e) {} return window.location + \"\";")} // ]]--> </SCRIPT> <SCRIPT language=javascript type=text/javascript> // <!--[CDATA[ function tinyMCE_ctl00_ctl00_bcr_bcr_PostForm_ctl04_PostBody_ctl00_Editor_handleEvent(e) { switch (e.type) { case "mouseup": case "keyup": window.tinyMCE_ctl00_ctl00_bcr_bcr_PostForm_ctl04_PostBody_ctl00_Editor_currentBookmark = tinyMCE.getInstanceById(tinyMCE.getEditorId('ctl00_ctl00_bcr_bcr_PostForm_ctl04_PostBody_ctl00_Editor')).selection.getBookmark(); break; case "beforedeactivate": case "blur": tinyMCE.getInstanceById(tinyMCE.getEditorId('ctl00_ctl00_bcr_bcr_PostForm_ctl04_PostBody_ctl00_Editor')).triggerSave(false,false,true); break; } return true; } tinyMCE.init({mode:"exact",elements:"ctl00_ctl00_bcr_bcr_PostForm_ctl04_PostBody_ctl00_Editor",relative_urls:false,handle_event_callback:"tinyMCE_ctl00_ctl00_bcr_bcr_PostForm_ctl04_PostBody_ctl00_Editor_handleEvent",theme:'advanced',theme_advanced_buttons1:'fontselect,separator,fontsizeselect,separator,forecolor,backcolor,separator,cut,copy,paste,pasteword,separator,code,iespell',theme_advanced_buttons2:'bold,italic,underline,strikethrough,separator,indent,outdent,separator,bullist,numlist,separator,link,unlink,image,smiley',theme_advanced_buttons3:'',theme_advanced_toolbar_location:'top',theme_advanced_toolbar_align:'left',theme_advanced_path:false,dialog_type:'modal',document_base_url:tinyMCE_CommunityServerOptions.GetBaseUrl(),fix_content_duplication:true,theme_advanced_resizing:true,theme_advanced_statusbar_location:'bottom',theme_advanced_resize_horizontal:false,verify_html:false,cleanup:false,remove_linebreaks:false,plugins:'contentselector,paste,smilies,iespell',doctype:'<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"-->'}); // ]]> </SCRIPT> <LINK rel=stylesheet type=text/css href="http://forums.thedailywtf.com/tiny_mce/jscripts/tiny_mce/themes/advanced/css/editor_ui.css">
    <LABEL id=ctl00_ctl00_bcr_bcr_PostForm_ctl04_TagsSubForm_ctl00_ctl00_ctl00 for=ctl00_ctl00_bcr_bcr_PostForm_ctl04_TagsSubForm_ctl00_Tags>Tags</LABEL>
    <INPUT id=ctl00_ctl00_bcr_bcr_PostForm_ctl04_TagsSubForm_ctl00_Tags size=70 name=ctl00$ctl00$bcr$bcr$PostForm$ctl04$TagsSubForm$ctl00$Tags><BUTTON onclick="Telligent_Modal.Open('/utility/TagSelector.aspx?TagEditor=ctl00_ctl00_bcr_bcr_PostForm_ctl04_TagsSubForm',400,350,null); return false;" type=submit>Select Tags...</BUTTON>
    I do wonder why all thedailywtf links are changed to null though...




  • @boomzilla said:

    @El_Heffe said:
    And just about anything is more amusing than copy/pasting Monty Python.

    That's true. The accents just don't come across, and without the stupid accents it's just not the same. But it's better than posting about video games. Maybe unless it was a Monty Python video game.

    Well that would just be a Complete Waste Of Time.



  • @Zemm said:

    @boomzilla said:
    @El_Heffe said:
    And just about anything is more amusing than copy/pasting Monty Python.

    That's true. The accents just don't come across, and without the stupid accents it's just not the same. But it's better than posting about video games. Maybe unless it was a Monty Python video game.

    Well that would just be a Complete Waste Of Time.

    LFTY



  • @Ben L. said:

    @Zemm said:
    @boomzilla said:
    @El_Heffe said:
    And just about anything is more amusing than copy/pasting Monty Python.

    That's true. The accents just don't come across, and without the stupid accents it's just not the same. But it's better than posting about video games. Maybe unless it was a Monty Python video game.

    Well that would just be a Complete Waste Of Time.

    LFTY

     

    You have wasted please enable JavaScript seconds of your life.


    Global time wasted since June 7th, 2010:

    Unknown



  • @Lorne Kates said:

    @Ben L. said:

    @Zemm said:
    @boomzilla said:
    @El_Heffe said:
    And just about anything is more amusing than copy/pasting Monty Python.

    That's true. The accents just don't come across, and without the stupid accents it's just not the same. But it's better than posting about video games. Maybe unless it was a Monty Python video game.

    Well that would just be a Complete Waste Of Time.

    LFTY

     

    You have wasted please enable JavaScript seconds of your life.


    Global time wasted since June 7th, 2010:

    Unknown

    So you're one of those.



  • @Ronald said:

    @Lorne Kates said:

    @Ben L. said:

    @Zemm said:
    @boomzilla said:
    @El_Heffe said:
    And just about anything is more amusing than copy/pasting Monty Python.

    That's true. The accents just don't come across, and without the stupid accents it's just not the same. But it's better than posting about video games. Maybe unless it was a Monty Python video game.

    Well that would just be a Complete Waste Of Time.

    LFTY

     

    You have wasted please enable JavaScript seconds of your life.


    Global time wasted since June 7th, 2010:

    Unknown

    So you're one of those.

    How do you propose I show you the amount of time you've been on a page without javascript?



  • @Ben L. said:

    How do you propose I show you the amount of time you've been on a page without javascript?

    Flash. Silverlight. Java applet. ActiveX control. All big winners.



  • @Ben L. said:

    How do you propose I show you the amount of time you've been on a page without javascript?

    Animated GIF



  • @Zemm said:

    @Ben L. said:
    How do you propose I show you the amount of time you've been on a page without javascript?

    Animated GIF
     

    frameset, with one frame being the page, and another being a just-tall-enough bottom frame with src="UserTime.php?user_id=1&page_id=2&visit_id=3"

    UserTime.php, of course,  just emits at 301 Redirect back to itself with a 1 second timeout.

    No, there are no sessions. Yes, the querystring values are unencoded.

    Version 2 of UserTime.php contains a hillarious attempt by a php "coder" to compensate for network lag.



  • @Lorne Kates said:

    frameset
     

    iframe would do fine.



  • @dhromed said:

    @Lorne Kates said:

    frameset
     

    iframe would do fine.

     

    Which is exactly why we must use a Frameset.

     



  • @Lorne Kates said:

    @dhromed said:

    @Lorne Kates said:

    frameset
     

    iframe would do fine.

     

    Which is exactly why we must use a Frameset.

     

     

    It's the only way to be sure.

     


Log in to reply