Results 1 to 3 of 3
  1. #1
    Platinum Lounger
    Join Date
    Feb 2001
    Location
    Yilgarn region of Toronto, Ontario
    Posts
    5,453
    Thanks
    0
    Thanked 0 Times in 0 Posts

    vb6 - how to change default MAKE location (Visual Sudio 6 Enterprise)

    I am wading through projects, one by one, compiling where I can, and discovering that some others need to be compiled and registered before some can be compiled. It's a great way to spend New Year's Day!

    With a project (*.vbp) loaded, I choose File, Make, and VB6 elects to save the compiled file (in this case a DLL) in the source directory.

    I don't want that. I want to save all my hesitant compiles into a different directory, such as c:temp, for the time being.

    I can't find a way to force VB6 to direct all compiled code to a specific directory.

    Is this possible at all? It's a pain browsing to my c:temp each time I compile.

  2. #2
    Platinum Lounger
    Join Date
    Dec 2000
    Location
    Queanbeyan, New South Wales, Australia
    Posts
    3,730
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: vb6 - how to change default MAKE location (Visual Sudio 6 Enterprise)

    Chris,

    Are you talking about a single project or lots of projects?

    On a single project, if you change the location for your compiled code, then save the project, that location will stick.
    Subway Belconnen- home of the Signboard to make you smile. Get (almost) daily updates- follow SubwayBelconnen on Twitter.

  3. #3
    Platinum Lounger
    Join Date
    Feb 2001
    Location
    Yilgarn region of Toronto, Ontario
    Posts
    5,453
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: vb6 - how to change default MAKE location (Visual Sudio 6 Enterprise)

    >change the location for your compiled code, then save the project, that location will stick.

    Lots of projects. I said 100, but it's more like 70.

    I have a sheet/table with path and project name printed on it, and I'm just over 2/3 the way down.

    "Lots" because although there are 70 names, some won't compile until I've compiled and registered the project code that is required, so for every project in the first 1/3, I'd compile it, determine it needs another, compile THAT and then go back and recompile the first. Some projects are dependant on code in three others with consequent increase in workload.

    For this 1st exploratory pass, the source code is drive K:, and I'm compiling to drive L:.

    I have a batch job (pasted below) that registers those DLL and OCX that fall into L:, but I think I should be registering any EXE that land there, too.

    After today I want to look at a means of batch compile. I'd rather have a batch job run three times to make three passes over the source code than sit here with the mouse.


    <pre>REM RegaAll.bat Christopher Greaves Tuesday, January 1, 2002

    :: The first parameter is optional and may be the regsvr32 switch /U

    :: Register all DLLs in the current directory
    for %%a in (*.dll) do call regone.bat %%a %1

    :: Register all OCXs in the current directory
    for %%a in (*.ocx) do call regone.bat %%a %1

    REM End of RegAll.bat
    </pre>


    <pre>REM UnRegaAll.bat Christopher Greaves Tuesday, January 1, 2002

    :: UN-Register all DLLs in the current directory

    call regall.bat /u

    REM End of UnRegAll.bat
    </pre>


    <pre>REM RegOne.bat Christopher Greaves Tuesday, January 1, 2002

    :: Register a single DLL

    :: The first parameter should be a file name
    :: The second parameter is optional and may be the regsvr32 switch /U

    c:windowssystemregsvr32 %1 /s %2

    REM End of RegOne.bat
    </pre>


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •