SharpDevelop Community

Get your problems solved!
Welcome to SharpDevelop Community Sign in | Join | Help
in Search

Corsavy Compilation Problems

Last post 09-27-2005 12:59 AM by DavidSrbecky. 16 replies.
Page 1 of 2 (17 items) 1 2 Next >
Sort Posts: Previous Next
  • 08-23-2005 4:21 AM

    Corsavy Compilation Problems

    I have tried to compile my Visual Studio 8 Solution with corsavy version from svn and because on this solution i have 27 projects on compilation i receive some error about cannot copying files because are in use
  • 08-23-2005 8:48 AM In reply to

    Re: Corsavy Compilation Problems

    We do expect problems in this area (sln & *proj files). However, in your case it could be problematic to diagnose. It does work with VS I assume? Do you compile in #develop with VS still open? On what kind of project does it happen - class library, exe? Are those referencing other projects in the solution? Can you reproduce with a smaller-scale project you'd be willing to send to us?

    Chris

  • 08-23-2005 10:45 AM In reply to

    Re: Corsavy Compilation Problems

    My is a commercial project and i use VS.NET 8 solution on this solution i have 27 projects and some of this are class library and i have some project that reference other project, i have seen the problem using dlls are after the first debugging, before this all are compiled succefull
  • 08-23-2005 11:12 AM In reply to

    Re: Corsavy Compilation Problems

    So to narrow it down:
    • when you start #develop, open your solution, build it, it works fine.
    • even rebuild all works
    • it stops working once you debug your project
    Correct?

    Chris

  • 08-23-2005 3:04 PM In reply to

    • DavidSrbecky
    • Top 10 Contributor
    • Joined on 08-22-2005
    • Usti nad Labem, Czech Republic
    • Posts 440
    • Team Members

    Re: Corsavy Compilation Problems

    Could you send the errors please or could you at least specify the type of the files that are in use? (like .exe , .dll , .pdb or other)

  • 08-24-2005 10:43 AM In reply to

    Re: Corsavy Compilation Problems

     ChristophWille wrote:
    So to narrow it down:
    • when you start #develop, open your solution, build it, it works fine.
    • even rebuild all works
    • it stops working once you debug your project

    Correct?

    Chris

     

    yes, after debug if i try to rebuild the project it stops working

    excuse me about my "maccaroni" english but i am italian ;)

     

  • 08-24-2005 2:23 PM In reply to

    Re: Corsavy Compilation Problems

    this is the output after debug.

     

    Build started.
    Build started.
    C:\WINDOWS\Microsoft.NET\Framework\v2.0.50215\Microsoft.Common.targets(0,0) : warning MSB3061: Unable to delete file "..\..\..\..\modus\moData.dll". Access to the path 'C:\Programmi\culturanuova\modus\moData.dll' is denied.
    C:\WINDOWS\Microsoft.NET\Framework\v2.0.50215\Microsoft.Common.targets(0,0) : warning MSB3061: Unable to delete file "..\..\..\..\modus\moBase.dll". Access to the path 'C:\Programmi\culturanuova\modus\moBase.dll' is denied.
    C:\WINDOWS\Microsoft.NET\Framework\v2.0.50215\Microsoft.Common.targets(0,0) : warning MSB3061: Unable to delete file "..\..\..\..\modus\moResources.dll". Access to the path 'C:\Programmi\culturanuova\modus\moResources.dll' is denied.
    C:\WINDOWS\Microsoft.NET\Framework\v2.0.50215\Microsoft.Common.targets(0,0) : warning MSB3061: Unable to delete file "..\..\..\..\modus\moControls.dll". Access to the path 'C:\Programmi\culturanuova\modus\moControls.dll' is denied.
    C:\WINDOWS\Microsoft.NET\Framework\v2.0.50215\Microsoft.Common.targets(0,0) : warning MSB3061: Unable to delete file "..\..\..\..\modus\moDialogs.dll". Access to the path 'C:\Programmi\culturanuova\modus\moDialogs.dll' is denied.
    C:\WINDOWS\Microsoft.NET\Framework\v2.0.50215\Microsoft.Common.targets(0,0) : warning MSB3061: Unable to delete file "..\..\..\..\modus\moPanels.dll". Access to the path 'C:\Programmi\culturanuova\modus\moPanels.dll' is denied.
    C:\WINDOWS\Microsoft.NET\Framework\v2.0.50215\Microsoft.Common.targets(0,0) : warning MSB3061: Unable to delete file "..\..\..\..\..\modus\ModusOP.exe". Access to the path 'C:\Programmi\culturanuova\modus\ModusOP.exe' is denied.
    Compiling moConfig
    Compiling moImaging
    Compiling moData
    C:\WINDOWS\Microsoft.NET\Framework\v2.0.50215\Microsoft.Common.targets(2274,9) : error MSB3021: Unable to copy file "obj\Debug\moData.dll" to "..\..\..\..\modus\moData.dll". The process cannot access the file '..\..\..\..\modus\moData.dll' because it is being used by another process.
    Compiling moResources
    C:\Programmi\culturanuova\modus_build_new\trunk\current\moResources\IconUtils.cs(91,28) : warning CS0649: Field 'Fireball.Windows.Utils.IconUtils.NullHandleRef' is never assigned to, and will always have its default value
    C:\WINDOWS\Microsoft.NET\Framework\v2.0.50215\Microsoft.Common.targets(2274,9) : error MSB3021: Unable to copy file "obj\Debug\moResources.dll" to "..\..\..\..\modus\moResources.dll". The process cannot access the file '..\..\..\..\modus\moResources.dll' because it is being used by another process.
    Compiling moLocals
    Build failed.

  • 08-24-2005 2:29 PM In reply to

    Re: Corsavy Compilation Problems

    We can reproduce this problem now.
    It does not have anything to do with debugging; but seems to be a problem with code completion.

    You can work around the problem by using project references instead of assembly references to the file.
    It's always better to use project references because otherwise a "Release" build would still use the libraries from the debug configuration.
    Daniel Grunwald
  • 08-24-2005 3:12 PM In reply to

    Re: Corsavy Compilation Problems

    rev 429 has a fix. See the announcement in this section on how to obtain the latest code from Subversion.

    Chris

  • 08-24-2005 4:05 PM In reply to

    Re: Corsavy Compilation Problems

    the problem persist :(
  • 08-24-2005 4:29 PM In reply to

    Re: Corsavy Compilation Problems

    The problem I fixed had nothing to do with debugging; but was problem with code completion when you had references to library files (references to projects worked ok).
    When your problem occurs only when debugging, then it's a different bug.
    Daniel Grunwald
  • 08-24-2005 5:27 PM In reply to

    Re: Corsavy Compilation Problems

    I tried the procedure I outlined (rebuild, debug, rebuild) with a winapp / classlib combo. It works fine for me. So please provide us with a sample that exhibits the problem, because I cannot repro.

    Chris

  • 09-02-2005 7:32 PM In reply to

    Re: Corsavy Compilation Problems

    I have exactly the same problem (in the 458 build), but with a "simple" project (no other project inclusion). When I debug it, I get an "Unable to delete the file icolorfolder.exe, another process is probably using it", etc etc.

    I've found a way to reproduce the bug using my project :
    http://membres.lycos.fr/kemenaran/iCF_bug.zip

    Now the procedure : open the project and start to Debug it. At a certain point, the program will throw an exeption to the Debugger because it can't find a file. Select "Ignore", then go to the Project Options and change something (I changed the command line arguments, for example). Save the Project Options, relauch a Debug, and the error occurs.

    I hope you'll be able to track the problem (and thanks a lot for your fantastic work anyway ^^).

  • 09-02-2005 7:39 PM In reply to

    Re: Corsavy Compilation Problems

    Warning: kemenaran's project uses "C:\Windows\Resources" as output directory.
    I changed the output directory, ran the program in the debugger and chose an icon. On the exception, I pressed "Break" and then "Stop process".
    After that, the file could not be recompiled (I did not have to change the project options; using Build>Rebuild Solution is enough to reproduce the error)
    Daniel Grunwald
  • 09-03-2005 2:47 AM In reply to

    Re: Corsavy Compilation Problems

    Well, after some hours of investigations, I think I've found (one of ?) the location of the problem. It seems that this bug actually occurs each time you :
    1. Lauch the debugger and exit it (by closing the program or stop the debugger).
    2. Change anything that has to be saved before the compilation (code, project options, etc)
    3. Lauch the debugger again : then the bug occurs.
    I browsed a bit the #develop sources, and found that the two XmlTextWriters of the Save Project function (located in ICSharpCode.SharpDevelop.Project.MSBuildProject, function Save(string fileName)) are causing the bug ; I believe that the equivalent function for Save Code has the same problem. I tried to debug these functions, but I can't see what's going wrong in this, neither why it doesn't occurs when you didn't lauch the Debugger once before modifying your files.

    I suppose this is a bug due to the instable nature of Corsavy and the debugger, do you think this should be moved to the bug report section (or maybe just discarded, waiting for a more stable debugger) ?

Page 1 of 2 (17 items) 1 2 Next >
Powered by Community Server (Commercial Edition), by Telligent Systems
Don't contact us via this (fleischfalle@alphasierrapapa.com) email address.