I also suspect that some update in either iOS, XCode, OS X, Xamarin Forms or some other packages is causing my problem. And because there are so many fragile dependencies in the Xamarin world, it's really hard to know who to blame. I will probably follow your suggestion and unreference everything and add it all back again. I hope I don't have to downgrade, as that would be more error-prone work -- *GK*
On 27 February 2017 at 15:56, David Richards <ausdot...@davidsuniverse.com> wrote: > Greg, > > I agree with you regarding Xamarin development. I can't believe how much > time I've wasted because of bugs in Xamarin. > > I've seen your problem before some time ago but I can't remember what the > solution was. These kinds of problems happen so often I stopped taking > notice and just start doing "magical" things to fix them. > > Things that I now try to fix mysterious problems that shouldn't occur: > - Close then reopen the solution. > - Quit and relaunch Xamarin Studio. > - Take note of the packages being used. Remove them all. Add them all back > again. Start with Forms as this will add many of them automatically. > > These are my day-to-day fixes that resolve 90% of mysterious problems. > > Last week there was an update. I made the mistake of installing this on > Thursday and it took all up a full day to fix the mess it made. The latest > version crashed when trying to open projects and seems to have changed the > way some projects are compiled. For example, in one class, it was skipping > functions altogether. I had to downgrade to fix it. > > I've also found references sometimes get messed up and can't be fixed > within Xamarin Studio. So I manually add them in the project files. > > David > > "If we can hit that bullseye, the rest of the dominoes > will fall like a house of cards... checkmate!" > -Zapp Brannigan, Futurama > > On 27 February 2017 at 14:27, Greg Keogh <gfke...@gmail.com> wrote: > >> Have you tried deleting the resource file (or all of them if more than >>> one) and creating a new one from scratch? Just a stab in the dark. >> >> >> Sort of, I added a fresh test resx file (leaving the old one) and it also >> generated the same error inside the GetString method. I also tried >> different cultures, including the invariant one, but no luck. I may as you >> say, remove ALL resx, clean, put one back and try again. I've got nothing >> to lose except more hours of my time - *GK* >> > >
