Right-click on the main project in the "Solution Explorer" sidebar pane on the left, and choose Project Dependencies. You have just added a project as a subproject. and navigate to the other project that you want as a subproject. Here are the steps I used to make it work:Ĭhoose File / Add / Existing Project. Now it will build the DLL, but it isn't linking things correctly yet the linker is complaining that the functions exported from the DLL are not available. I tried repeating the above steps for the EXE project. Visual Studio seems to have then magically set up the link dependency for me, and when I hit the F7 key in the DLL project, it will build the static library project. and set that the DLL project depends on the static library project, which should build first. (This is only available on the File menu as far as I can tell! It definitely is not in the right-click menu.) Second, I clicked on the DLL project in the "Solution Explorer" sidebar on the left, then right-clicked and chose Project Dependencies. First, in the DLL project, I used File / Add and then chose Add Existing Project to add the static library. If I set up the subprojects correctly, will this Just Work automatically?ĮDIT: I have made progress. lib file from the DLL likewise when I rebuild the EXE as Release, it should link with the Release. When I rebuild the EXE as Debug, it should link with the Debug. I'd like to just have the EXE open, hit the F7 key, and everything builds. When I rebuild the EXE, it should rebuild the DLL if need be, and in turn the DLL build should rebuild the static library if need be. Right now I have three separate VS2010 projects, but I know it is possible to set things up as "subprojects": the static library should be a subproject of the DLL, and the DLL should be a subproject of the EXE. (I am using "implicit" DLL linking I do not need to control the DLL loading and unloading.) The DLL should have the static library linked in, and the executable depends on the DLL. I am working on several related projects: a static library, a DLL, and an executable.
OFFICETIME SUBPROJECT CODE
This post was originally published by EPM Strategy.I am developing Windows code in C using Visual Studio 2010.
If we had hovered over that indicator we would have seen that it states “This project was inserted read-only from” and then gives the path to the subproject. Going back to the screen shot from before, you can see next to the indicator column a small red indicator next to the subproject indicator. Quick side note: Was there any way we could have known this BEFORE we made changes to the subproject which we subsequently lost when we changed it from Read Only and had to close and re-open Professional? Yes, there is an indicator. Make sure that is not selected.Īfter doing this change though, you have to close Project and re-open it. Just go into the properties for subproject by double clicking on the name of the subproject, and then go to the Advanced tab. How do I resolve this? Luckily, it is not that hard to make the subproject saveable and no longer read only. But, I do not want to do that, I want the subproject as I have it. And, the system gives me a chance to save a copy of the file with changes. HOWEVER, I now get the error message that the subproject is a read-only file. As expected, I get the following message: So, I make my modifications and then select the Save button.
It appears like this in Project Professional.Īt the top of the screen is the name of the schedule (MasterProject) but it does NOT say “read only”. In this example, I have a Master Project, which is titled the highly original name of “Master Project,” and I have an equally cleverly named subproject named “SubProject”.
OFFICETIME SUBPROJECT HOW TO
This quick post is how to resolve that issue.
OFFICETIME SUBPROJECT PROFESSIONAL
Sometimes when you are using Microsoft Professional and you insert a Subproject, the Subproject is “Read Only” when you try to save the Master Project.