3.0.8, Cannot Compile in VS2003

Last post 02-25-2005 11:34 AM by cniknet. 13 replies.

Sort Posts:

  • 3.0.8, Cannot Compile in VS2003

    01-07-2005, 8:40 AM
    • Participant
      770 point Participant
    • jonhsv
    • Member since 02-11-2003, 11:18 AM
    • Posts 156
    Hi


    I receive those error when I try to run my project in Debug mode in Visual Studio 2003, I have tried to restart my computer to kill the proccess


    Anyone ?


    Regards


    Jón Sveinsson


    Cannot copy assembly 'DotNetNuke.WebControls' to file 'C:\DNN308\bin\DotNetNuke.WebControls.dll'. The process cannot access the file because it is being used by another process.

    Cannot copy assembly 'DotNetNuke.WebUtility' to file 'C:\DNN308\bin\DotNetNuke.WebUtility.dll'. The process cannot access the file because it is being used by another process.

    Unable to write to output file 'C:\Documents and Settings\jon\VSWebCache\JONHS-XP\DNN308\obj\Debug\DotNetNuke.dll': System Error &H80070020&
    Unable to write to output file 'C:\Documents and Settings\jon\VSWebCache\JONHS-XP\DNN308\obj\Debug\DotNetNuke.pdb': System Error &H80070005&

  • Re: 3.0.8, Cannot Compile in VS2003

    01-07-2005, 10:38 AM
    • Member
      40 point Member
    • jrASPx
    • Member since 11-06-2003, 10:31 PM
    • Posts 8
    Jón,

    I had a similar problem and I constantly had to close VS.NET, delete the cached folder (c:\Documents and Settings\YourProfile\VSWebCache\YourServerName\dnnXXX), and then open VS.Net again and it would work for a while.

    Somehow (probably google) I figured out to go into the refrences in VS.Net and look at the properties of the offending dll(s). Change the "Copy Local" property to true. This fixed the problem I was having. Have never had it happen since.

    Hope this helps...

    José
  • Re: 3.0.8, Cannot Compile in VS2003

    01-07-2005, 10:38 AM
    • All-Star
      16,504 point All-Star
    • hooligannes97
    • Member since 09-26-2003, 2:57 PM
    • Bolivia
    • Posts 2,917
    • Moderator
    Your developing set up is missing some configs, read www.dotnentuke.dk to understand whow it should be configured.
    Do you know the truth when you hear it?
  • Re: 3.0.8, Cannot Compile in VS2003

    01-07-2005, 10:45 AM
    • Contributor
      2,484 point Contributor
    • toddhd
    • Member since 06-18-2002, 10:03 AM
    • Edina, MN
    • Posts 527
    Actually the error message doesn't say they are missing, it says they are in use.

    It could be that you have Index Server running on your machine. If so, exclude your DNN directory from the Indexing. In Windows XP, you'd right click on the DotNetNuke folder, select properties, then click the Advanced button. Make sure the checkbox that says "For fast searching..." is NOT checked.

    You could alternatively use the Computer Management console to access Index server and exclude the directory there.

    Make sure you reboot after this change to make it take effect, then see if that helps. If not, let me know, it could be several things.
    -Todd Davis
    http://www.SeaburyDesign.com
  • Re: 3.0.8, Cannot Compile in VS2003

    01-07-2005, 10:53 AM
    • Member
      105 point Member
    • bbrian
    • Member since 04-20-2004, 3:33 PM
    • Posts 21
    I have had this same problem and it is definitely the index server causing it. Like toddhd says, add the DNN directory to the exclusion list of the Index server, but you also need to add your vswebcache directory to the exclusion list as well:
    C:\Documents and Settings\jon\VSWebCache\

    If you don't want to add the exclusions, you can also restart the index service just before you build and it will generally allow you to build it.
    -Brian Brown
  • Re: 3.0.8, Cannot Compile in VS2003

    01-07-2005, 10:59 AM
    • Contributor
      2,484 point Contributor
    • toddhd
    • Member since 06-18-2002, 10:03 AM
    • Edina, MN
    • Posts 527
    Just to be fair, jrASPx is correct too about the "Copy Local" causing this problem - however, that shouldn't be a problem if you are only compiling the unmodified DNN solution and projects. They already have the "copy local" attributes set properly.

    If you have added your own custom projects to the DNN solution, then that is a different story. In that case, make sure that any references to DNN dll's that you make are set to CopY Local = False as he noted above. You should also go into the solution properties and uncheck all the DNN projects so that they don't rebuild each time.

    But I'm getting ahead of myself. Let us know where you are at, and if the problem is resolved.
    -Todd Davis
    http://www.SeaburyDesign.com
  • Re: 3.0.8, Cannot Compile in VS2003

    01-07-2005, 11:40 AM
    • All-Star
      16,504 point All-Star
    • hooligannes97
    • Member since 09-26-2003, 2:57 PM
    • Bolivia
    • Posts 2,917
    • Moderator
    Unless you are modifying the core, you shouldn't keep building it. So you can modify the configuration to just build your project.
    Do you know the truth when you hear it?
  • Re: 3.0.8, Cannot Compile in VS2003

    01-07-2005, 11:43 AM
    • All-Star
      16,504 point All-Star
    • hooligannes97
    • Member since 09-26-2003, 2:57 PM
    • Bolivia
    • Posts 2,917
    • Moderator
    Just to clarifyTodd, I didn't say the dll's where missing I said some configurations where missing.
    Do you know the truth when you hear it?
  • Re: 3.0.8, Cannot Compile in VS2003

    01-07-2005, 5:15 PM
    • Participant
      770 point Participant
    • jonhsv
    • Member since 02-11-2003, 11:18 AM
    • Posts 156
    Thanks Guys

    That was the trick, I excluded those folder for fast Search and Whola... it works


    Regards


    Jón Sveinsson
  • Re: 3.0.8, Cannot Compile in VS2003

    01-07-2005, 5:49 PM
    • Participant
      770 point Participant
    • jonhsv
    • Member since 02-11-2003, 11:18 AM
    • Posts 156
    Hi

    One question, I tried to create new Project in the solution, And added DotNetNuke as a reference to it, Created some new usercontrol with one Label, but when I tried to run it from the VS2003, I receive the following error, I have excluded the 2 folder from the Indexing server, I even tried to stop the Indexing server. when I delete the project from the Solution everything works fine, The Project I added is C# Project which I'm not sure if I can add it directly to the solution or do I have to use instructions from Bonosoft from www.DotNetNuke.dk

    Regards

    Jón Sveinsson


    Unable to write to output file 'C:\Documents and Settings\jon.JONHS-XP\VSWebCache\JONHS-XP\DNN308\obj\Debug\DotNetNuke.dll': System Error &H80070020&
  • Re: 3.0.8, Cannot Compile in VS2003

    01-07-2005, 7:51 PM
    • Contributor
      2,484 point Contributor
    • toddhd
    • Member since 06-18-2002, 10:03 AM
    • Edina, MN
    • Posts 527
    First, I would just delete the whole \DNN308 Folder under \VSWebCache altogether. That might solve a lot of issues for you. It will rebuild itself later.

    After that, exclude the whole C:\Documents and Settings folder from Index Server. (In fact, unless you have some particular reason you need Index Server running, just turn it off altogether.)
    -Todd Davis
    http://www.SeaburyDesign.com
  • Re: 3.0.8, Cannot Compile in VS2003

    01-08-2005, 6:58 PM
    • Participant
      770 point Participant
    • jonhsv
    • Member since 02-11-2003, 11:18 AM
    • Posts 156
    Hi


    I have deleted the \DNN308 folder and I tried to exclude the whole c:\Documents and settings, I event tried to stop the Indexing server, but still I always receive the same error
    Have anyone here created a C# Module in the DNN 3.0.8

    What can be wrong here ?

    Regards

    Jon Sveinsson


    Unable to write to output file 'C:\Documents and Settings\jon.JONHS-XP\VSWebCache\JONHS-XP\DNN308\obj\Debug\DotNetNuke.dll': System Error &H80070020&

  • Re: 3.0.8, Cannot Compile in VS2003

    02-25-2005, 11:25 AM
    • Member
      20 point Member
    • RCCrash
    • Member since 06-05-2003, 12:28 PM
    • Posts 4
    http://support.microsoft.com/default.aspx?scid=kb;en-us;313512

    Bug in VS.NET. I'm working on 3 sites right now and building a couple modules a day. I'm spending more time on this issue than I am writing code!

    DNN guys, what are you doing with this issue? Is it possible to build my project in a different solution? If so, are there special configurations I need to use to integrate it with DNN besides copying the assembly to the core/bin directory?

    Thanks for any info.
  • Re: 3.0.8, Cannot Compile in VS2003

    02-25-2005, 11:34 AM
    • Star
      9,585 point Star
    • cniknet
    • Member since 07-23-2002, 3:19 PM
    • Washington, DC
    • Posts 1,915
    I think the solution I posted might work for you as it eliminates references to all DNN projects.

    view post 839442

    Nik


    Nik Kalyani
    Speerio, Inc.

    [DotNetNuke and ASP.Net solutions here]
Page 1 of 1 (14 items)