I forget the fix to this every time, so posting here to remember.
First, set the Project > Web Use Local URL and fill in Override application root URL. It will want to create a virtual directory. Let it, then remove it in IIS after debugging starts.
I know there must be a better fix, but this gets it moving when in a hurry.
First issue was:
“Invalid element <msbuild>. Unknown task or datatype.”
Found the basic solution at http://www.kaizengrove.com/blog/2010/06/30/fixed-invalid-element-unknown-task-or-datatype/, which was that Nant-contrib was required for some reason. To make life easy, I just dropped the files from the bin in the contrib project into my Nant bin.
Then I hit:
[msbuild] E:DLT_SVNWebGNMA.RFS.Web.csproj(189,11): error MSB4019: The imported project “C:Program FilesMSBuildMicrosoftVisualStudiov9.0WebApplicationsMicrosoft.WebApplication.targets” was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.
$(MSBuildExtensionsPath) on my 64 bit machine resolved to the path of a 32 bit machine because Nant is compiled as a 32 bit program. Argh. So:
set MSBuildExtensionsPath=C:Program Files (x86)MSBuild
I received a notice that I was in the top 5% of viewed profiles. I just saw a post from someone in the top 1%. In my case, I don’t do anything more than keep my profile up to date, and been a member since 2002.
Feel free to post your comment here about your LinkedIn percent.
I noted yesterday about Where to Put Your WebCenter Producer Connections that the process for making it an IDE connection still started in the Application panel. Now I know why. I added another portlet to the producer and it shows up in the IDE Connection resources but would not drag into the application. Leaving off a few hours of frustrated Googling, I eventually went to the connection in the Application resources and discovered that the Producer had to be refreshed there in order to make it available to the application. Other than a reference point, I don’t see the reason to even have in the IDE panel now that I see how it works.
When creating a WSRP connection, the documentation says “For other methods of invoking the wizard, such as from the Resource Palette, see Section 1.6.2, “How Do I Access the Connection Wizards?” (64.2.1 How to Register a WSRP Portlet Producer) but in the case of WSRP producers, for both Resource Palette and Application Navigator, you invoke the wizard from the Application Navigator and then choose where the connection will be stored:
