Hi Alan

On 2011.11.10 14:27, Alan wrote:
Hi,

Answers inline...

The log file is overwritten every time MonoDevelop is started. The next release of MonoDevelop should a couple of log files around so that it's possible to retrieve an older log file for diagnostic purposes.

OK. lound and clear... sorry logs are lost for that problem I had...

     1. I posted a question few days ago about snippet concept in
        MonoDevelop.
        Can I reuse VS snippets and where to drop them? Are there
        separate snippets
        (code templates) system wide and per-user.

I haven't come across the question yet, but to the best of my knowledge code templates are stored in the monodevelop global preferences so they will always be system-wide. There is no way that I know of to do user specific ones. You can edit the snippets and add new ones by clicking on MonoDevelop -> Preferences and going to the 'Code Templates' section of the TextEditor preferences.

OK. This would be "manual", but can I use bunch of *.snippet files from VS in MonoDevelop
and where to "drop" those?

the question was posted on 2011-11-03 under subject: [MonoDevelop] Code templates location

It is no rush, we are working on our project and in parallel improving our infrastructure and environment (snippets, project and item templates). most are for MonoDroid, but right now
begginig on MonoTouch stuff...

regards

mel

Alan


    Thanks,
    No thank You one more time.

    greetings...


    Alan

    On 8 November 2011 12:04, Miljenko Cvjetko
    <mcvje...@holisticware.net <mailto:mcvje...@holisticware.net>> wrote:

        Hi

        see inline...


        On 2011.11.08 12:31, Alan wrote:
        Hi,

        This is actually the most bizarre issue I've ever seen. The
        code path which throws the 'Mono for Android is not
        installed' error is *identical* for the case where you open
        an existing project and the case where you start a new
        project. The first time the Mono for Android code is
        touched, a static constructor runs which essentially
        verifies that the file
        
"/Developer/MonoAndroid//usr/lib/mandroid/Mono.Android.DebugRuntime-debug.apk"
        exists, which it does.

        However, if the file is *not* detected, then Mono for
        Android is marked as not being installed and the information
        in the about dialog will display "Mono for Android not
        installed", which yours does. The code which populates the
        information in the about dialog is
        https://gist.github.com/c29a1fd1aaf2bcbf2075 . The code
        which pops up the error dialog is:
        https://gist.github.com/b34533235d56f4382e28 . This variable
        is only assigned to once so it is impossible for you to be
        unable to open an existing project and yet able to create a
        new one unless something has gone horrifically wrong in Mono.

        Our MacOSX guru took a bit time and deinstalled few things
        with AppZap... I believe only
        Mono4Android and MonoDevelop.
        Did reinstall and reboot after each install (just to be sure)...

        Now I can open ApiDemo.sln (old solution) w/o problems and it
        runs...

        Guru from above did fresh install of Lion, Xcode, AppleSDK
        and Monotouch.
        I have continued (with heavy fighting with kbd shortcuts,
        inverse mouse scrolling) MonoForAndroid
        installation, so it could be I did something wrong. I suspect
        that I tried to install more things
        at once so installation just went wrong.

        We'll keep You informed.


        The log file should be found at
        /Users/moljac/Library/Logs/MonoDevelop-2.8/MonoDevelop.log .
        You missed the 'Logs' part of the path when you checked
        before. I'd love a log file from immediately after you try
        to open an existing project and it fails and also from when
        you create a new android project and it doesn't throw an
        exception.

        Found it... Right now I'm on windoze box, so I'll send it tou
        You ASAP.



        If you can repeatedly get this issue when opening existing
        projects I'll sort out a special debug build which contains
        *much* more logging to try and figure out exactly what has
        gone wrong.

        I believe this is not neccessary, because right now guys are
        testing and 4th-5th solution
        opened w/o problems.

        But log will be sent to You...

        thanks & regards


        mel



-- Miljenko Cvjetko dipl.ing. ET
                Direktor/CEO
                Projektant rješenja/Solution Architect  
                Razvojni programer/Senior developer
                Voditelj projekta/Project Manager

        IX južna obala 13
        Kajzerica Zagreb
        T: 385 1 7775555
        M: 385 91 557 447 3
        F: 385 1 7779556
        e:mcvje...@holisticware.net  <mailto:mcvje...@holisticware.net>
        w:http://www.holisticware.net




-- Miljenko Cvjetko dipl.ing. ET
        Direktor/CEO
        Projektant rješenja/Solution Architect  
        Razvojni programer/Senior developer
        Voditelj projekta/Project Manager

    IX južna obala 13
    Kajzerica Zagreb
    T: 385 1 7775555
    M: 385 91 557 447 3
    F: 385 1 7779556
    e:mcvje...@holisticware.net  <mailto:mcvje...@holisticware.net>
    w:http://www.holisticware.net




--
Miljenko Cvjetko dipl.ing. ET
        Direktor/CEO
        Projektant rješenja/Solution Architect  
        Razvojni programer/Senior developer
        Voditelj projekta/Project Manager

IX južna obala 13
Kajzerica Zagreb
T: 385 1 7775555
M: 385 91 557 447 3
F: 385 1 7779556
e: mcvje...@holisticware.net
w: http://www.holisticware.net

_______________________________________________
Monodroid mailing list
Monodroid@lists.ximian.com

UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid

Reply via email to