Quantcast
Channel: Node.js Tools for Visual Studio
Viewing all articles
Browse latest Browse all 4630

New Post: Converting raw Node.js worker role to NTVS project

$
0
0
Ok so I inspected the .ccproj file and found
<ProjectReference Include="..\SocketWorker\SocketWorker.njsproj">
  <Name>SocketWorker</Name>
  <Project>{cdb85034-fd37-44bb-bae5-6b88050d2d82}</Project>
  <Private>True</Private>
  <RoleType>Web</RoleType>
  <RoleName>SocketWorker</RoleName>
  <UpdateDiagnosticsConnectionStringOnPublish>True</UpdateDiagnosticsConnectionStringOnPublish>
</ProjectReference>
Changed the role type to Worker and does not check for web.config now.

However met a further blocking check

C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Windows Azure Tools\2.4\Microsoft.WindowsAzure.targets(2880,5): warning : CloudServices67 : The entrypoint for role SocketWorker is already defined in the service definition file. Ignoring entrypoint Microsoft.NodejsTools.WebRole.dll.
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Windows Azure Tools\2.4\Microsoft.WindowsAzure.targets(2880,5): warning : CloudServices67 : The entrypoint for role SocketWorker is already defined in the service definition file. Ignoring entrypoint Microsoft.NodejsTools.WebRole.dll.
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Windows Azure Tools\2.4\Microsoft.WindowsAzure.targets(2880,5): error : CloudServices35 : An SSL certificate was not specified for the https input endpoint 'HttpsIn' of role SocketWorker.
Done building project "cloudservice.ccproj" -- FAILED.

I have a HTTPS endpoint defined which uses a self-bundled SSL cert in a config folder; on startup, the app code loads that SSL cert. This works fine with our current worker role implementation; how can this check be bypassed?

Viewing all articles
Browse latest Browse all 4630

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>