Databases
StackOverflow2013
Postsdbo
POMissingMethodException w/ Method present -> nerve-racking VS2010 bug?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMissingMethodException w/ Method present -> nerve-racking VS2010 bug?
    primarykey
    data
    text
    <p>For two days now I have a really pesky problem with VS 2010 (SP 1). My solution consists of 1 Azure project with 4 roles with each 1 instance. Each one of them executes a configuration change at one of the first lines to set the date format for the ServiceStack.Text JSON Serializer.</p> <pre><code>JsConfig.DateHandler = JsonDateHandler.ISO8601; </code></pre> <p>One would think there isn't much that can go wrong here, but somehow my VS thinks otherwise.. If I execute a Clean+Rebuild, the solution works just fine. If I stop the debugging (or some other exception ends the debug run), every further debug run will stop at this line and throw a MissingMethodException <img src="https://i.stack.imgur.com/AW3Wa.png" alt="thrown exception"> . </p> <p>If I do a Clean+Rebuild again, it works for exactly 1 run and then the exception gets thrown again. Obviously the method can't just vanish, but I am out of ideas about what could be the source of this problem and it just destroys my efficiency to Clean+Rebuild after E V E R Y single change.</p> <p>The previous ServiceStack.Text version did indeed not have this method (and yes, I used the previous version as of a few days ago), but I removed every single bit of it. I even looked at typeof(JsConfig).Assembly via QuickWatch to confirm that it loaded the latest version, which it did, so I can't imagine how the previous version could be responsible.</p> <p>Actions which I already tried but didn't change anything:</p> <ul> <li>Removed the .suo</li> <li>Deactivated AV and SearchProtocolHost (maybe they locked the file or something)</li> <li>Removed everything ServiceStack.Text-related via NuGet and reinstalled it in every (using) project</li> <li>Restarted VS2010 half a billion times</li> <li>Rebooted</li> <li>Looked for something obvious in Sysinternals Process Monitor</li> </ul> <p>Btw. I don't think this problem is really related to the ServiceStack.Text Library, but obviously I can't know that for sure. </p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USPharao2k
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POMissingMethodException w/ Method present -> nerve-racking VS2010 bug?
      1. USPharao2k
      1. VTBountyStart
    2. VO
      singulars
      1. POMissingMethodException w/ Method present -> nerve-racking VS2010 bug?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POMissingMethodException w/ Method present -> nerve-racking VS2010 bug?
      1. USLarsi
      1. VTFavorite
    1. COI got the same MissingMethod exception (@ JsConfig.DateHandler = JsonDateHandler.DCJSCompatible;) when I host my code in a service. But running it in a unittest it runs fine everytime. I feel your frustation... Please update if you figure this out
      singulars
      1. POMissingMethodException w/ Method present -> nerve-racking VS2010 bug?
      1. USLarsi
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload