Commented Issue: npm Package manager fails to retrieve published package list [1252]

September 3, 2014, 3:12 am

≫ Next: Commented Unassigned: 2.5GB memory spike opening project [1349]

≪ Previous: Reviewed: 1.0 Beta 2 (Sep 02, 2014)

$

0

0

Sometimes, when I right click npm and select "Manage npm Modules", the package manages says "Loading published package list", but it comes back empty. See screenshot here: 

I am still able to install packages using the npm command, but they are not added to packages.json and I have to call npm init manually.
Comments: Also getting the same issue, happened after I updated to Beta 2

---

Commented Unassigned: 2.5GB memory spike opening project [1349]

September 3, 2014, 10:37 am

≫ Next: Edited Issue: no completions on buffer instance [1077]

≪ Previous: Commented Issue: npm Package manager fails to retrieve published package list [1252]

$

0

0

Just upgraded from the 1.0 Alpha to 1.0 Beta 2 and during the project load memory usage spikes up to 2.3GB and stays there. CPU usage fluctuating between 50-70% and this is without even doing anything.

Just to elaborate on what my solution looks like, I have an Azure Cloud Services project and 3 other Class Library projects (2 of which are linked from the Cloud Services project). I have attached my packages.json file for you (incase it could be related to a particular package).

Memory issues were the very reason I have avoided upgrading so far but according to the feedback and release notes these where *supposed* to have been resolved.

I pretty much can't use this now I am going to have to revert back to Alpha build. If there is anything else I can send you for diagnostics let me know.

**Environment**
Windows 8.1
VS2013 Premium Update 1
Comments: nene: Can you describe what you mean by 6GB? VS is a 32-bit process and therefore shouldn't be capable of exceeding (roughly) 4GB of memory.

Edited Issue: no completions on buffer instance [1077]

September 3, 2014, 10:42 am

≫ Next: Edited Issue: Need to specialize array.push [1193]

≪ Previous: Commented Unassigned: 2.5GB memory spike opening project [1349]

$

0

0

new require('buffer').Buffer() / require('buffer').Buffer() gives no completions after

Edited Issue: Need to specialize array.push [1193]

September 3, 2014, 10:42 am

≫ Next: Commented Issue: We should understand `util.inherits` [1259]

≪ Previous: Edited Issue: no completions on buffer instance [1077]

$

0

0

Mongoose quick start does:

```
var db = mongoose.connection;
db.on('error', console.error.bind(console, 'connection error:'));
db.once('open', function callback () {
// yay!
});
```

connection is ultimately determined by an array which has a value pushed in, and so we get no completions on db because we know nothing about it's type.

We also don't get the on methods probably because we're not understanding:
```
Connection.prototype.__proto__ = EventEmitter.prototype;
```

Commented Issue: We should understand `util.inherits` [1259]

September 3, 2014, 10:43 am

≫ Next: Edited Issue: We should understand `util.inherits` [1259]

≪ Previous: Edited Issue: Need to specialize array.push [1193]

$

0

0

It is an idiomatic way to establish "inheritance" (i.e. prototype chain) between constructors in node. We should special-case it.

http://nodejs.org/api/util.html#util_util_inherits_constructor_superconstructor
Comments: This is already implemented

Edited Issue: We should understand `util.inherits` [1259]

September 3, 2014, 10:43 am

≫ Next: Edited Issue: socket.io - 'on' is missing in completions [983]

≪ Previous: Commented Issue: We should understand `util.inherits` [1259]

$

0

0

It is an idiomatic way to establish "inheritance" (i.e. prototype chain) between constructors in node. We should special-case it.

http://nodejs.org/api/util.html#util_util_inherits_constructor_superconstructor

Edited Issue: socket.io - 'on' is missing in completions [983]

September 3, 2014, 12:01 pm

≫ Next: Commented Issue: socket.io - 'on' is missing in completions [983]

≪ Previous: Edited Issue: We should understand `util.inherits` [1259]

$

0

0

```
var sio = require('socket.io').listen(80);
sio.sockets.on
```

There's no member `on` in the member list for `sockets`. Most other stuff seems to be there, just not this.

Commented Issue: socket.io - 'on' is missing in completions [983]

September 3, 2014, 12:01 pm

≫ Next: Commented Issue: body-parser member info missing [1239]

≪ Previous: Edited Issue: socket.io - 'on' is missing in completions [983]

$

0

0

```
var sio = require('socket.io').listen(80);
sio.sockets.on
```

There's no member `on` in the member list for `sockets`. Most other stuff seems to be there, just not this.

Comments: This appears to be working now.

---

Commented Issue: body-parser member info missing [1239]

September 3, 2014, 12:36 pm

≫ Next: Commented Issue: body-parser member info missing [1239]

≪ Previous: Commented Issue: socket.io - 'on' is missing in completions [983]

$

0

0

```js
var bodyParser = require('body-parser');
bodyParser();
bodyParser.json();
```
`bodyParser` only displays members that are universal to all objects - no info when calling it or on `json`.

It seems that we don't correctly understand the following code in body-parser/index.js:
```
var deprecate = require('depd')('body-parser')
exports = module.exports = deprecate.function(bodyParser,
'bodyParser: use individual json/urlencoded middlewares')
```

This is meant to show a deprecation message when people call `bodyParser` as a function (you're supposed to use `json` and other members now). But it looks like it screws our ability to parse exports entirely for this module.
Comments: The issue here is actually this code: ``` var parsersDir = path.join(__dirname, 'lib', 'types') /** * Auto-load bundled parsers with getters. */ fs.readdirSync(parsersDir).forEach(function onfilename(filename) { if (!/\.js$/.test(filename)) return var loc = path.resolve(parsersDir, filename) var mod var name = path.basename(filename, '.js') function load() { if (mod) { return mod } return mod = require(loc) } Object.defineProperty(exports, name, { configurable: true, enumerable: true, get: load }) }) ``` Which we also need to understand elsewhere.

Commented Issue: body-parser member info missing [1239]

September 3, 2014, 12:37 pm

≫ Next: Created Issue: Analysis caused crash? [1375]

≪ Previous: Commented Issue: body-parser member info missing [1239]

$

0

0

```js
var bodyParser = require('body-parser');
bodyParser();
bodyParser.json();
```
`bodyParser` only displays members that are universal to all objects - no info when calling it or on `json`.

It seems that we don't correctly understand the following code in body-parser/index.js:
```
var deprecate = require('depd')('body-parser')
exports = module.exports = deprecate.function(bodyParser,
'bodyParser: use individual json/urlencoded middlewares')
```

This is meant to show a deprecation message when people call `bodyParser` as a function (you're supposed to use `json` and other members now). But it looks like it screws our ability to parse exports entirely for this module.
Comments: This is the elsewhere: https://nodejstools.codeplex.com/workitem/1085

Created Issue: Analysis caused crash? [1375]

September 3, 2014, 12:58 pm

≫ Next: Edited Issue: Analysis caused crash? [1375]

≪ Previous: Commented Issue: body-parser member info missing [1239]

$

0

0

Using build 20903.00, VS 2013 Update 3
I had the task explorer extension installed, with the task explorer tool window opened, but there was nothing in it. I don't know if it's related yet, will update if I find out.

```
Application: devenv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.InteropServices.SEHException
Stack:
at Microsoft.VisualStudio.Editor.Implementation.SimpleTextViewWindow.Init_InitializeWpfTextView()
at Microsoft.VisualStudio.Editor.Implementation.SimpleTextViewWindow.Init_OnActivation()
at Microsoft.VisualStudio.Editor.Implementation.SimpleTextViewWindow.get_WpfTextViewHost()
at Microsoft.VisualStudio.Editor.Implementation.SimpleTextViewWindow.GetData(System.Guid ByRef, System.Object ByRef)
at Microsoft.VisualStudio.Editor.Implementation.VsEditorAdaptersFactoryService.GetWpfTextViewHostFromVsTextView(Microsoft.VisualStudio.TextManager.Interop.IVsTextView)
at Microsoft.VisualStudio.Editor.Implementation.VsEditorAdaptersFactoryService.GetWpfTextView(Microsoft.VisualStudio.TextManager.Interop.IVsTextView)
at Microsoft.NodejsTools.Intellisense.VsProjectAnalyzer.GetOpenSnapshot(Microsoft.NodejsTools.Analysis.IProjectEntry)
at Microsoft.NodejsTools.Intellisense.VsProjectAnalyzer.ParseFile(Microsoft.NodejsTools.Analysis.IProjectEntry, System.String, System.IO.Stream)
at Microsoft.NodejsTools.Intellisense.VsProjectAnalyzer+<>c__DisplayClass6.<EnqueueFile>b__5()
at Microsoft.NodejsTools.Intellisense.VsProjectAnalyzer+<>c__DisplayClass9.<EnqueWorker>b__8(System.Object)
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()
```

Edited Issue: Analysis caused crash? [1375]

September 3, 2014, 1:05 pm

≫ Next: Edited Issue: Analysis caused crash? [1375]

≪ Previous: Created Issue: Analysis caused crash? [1375]

$

0

0

Using build 20903.00, VS 2013 Update 3
Edit: Not related to task explorer extension (repros without it)

Create starter express project.
Add new blank JavaScript file named grunt.js to project.
Close solution, save when prompted.
Reload solution and wait a few seconds.
If it doesn't repro, restart VS and reload solution.

```
Application: devenv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.InteropServices.SEHException
Stack:
at Microsoft.VisualStudio.Editor.Implementation.SimpleTextViewWindow.Init_InitializeWpfTextView()
at Microsoft.VisualStudio.Editor.Implementation.SimpleTextViewWindow.Init_OnActivation()
at Microsoft.VisualStudio.Editor.Implementation.SimpleTextViewWindow.get_WpfTextViewHost()
at Microsoft.VisualStudio.Editor.Implementation.SimpleTextViewWindow.GetData(System.Guid ByRef, System.Object ByRef)
at Microsoft.VisualStudio.Editor.Implementation.VsEditorAdaptersFactoryService.GetWpfTextViewHostFromVsTextView(Microsoft.VisualStudio.TextManager.Interop.IVsTextView)
at Microsoft.VisualStudio.Editor.Implementation.VsEditorAdaptersFactoryService.GetWpfTextView(Microsoft.VisualStudio.TextManager.Interop.IVsTextView)
at Microsoft.NodejsTools.Intellisense.VsProjectAnalyzer.GetOpenSnapshot(Microsoft.NodejsTools.Analysis.IProjectEntry)
at Microsoft.NodejsTools.Intellisense.VsProjectAnalyzer.ParseFile(Microsoft.NodejsTools.Analysis.IProjectEntry, System.String, System.IO.Stream)
at Microsoft.NodejsTools.Intellisense.VsProjectAnalyzer+<>c__DisplayClass6.<EnqueueFile>b__5()
at Microsoft.NodejsTools.Intellisense.VsProjectAnalyzer+<>c__DisplayClass9.<EnqueWorker>b__8(System.Object)
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()
```

Edited Issue: Analysis caused crash? [1375]

September 3, 2014, 4:12 pm

≫ Next: Created Unassigned: Can't publish native node packages [1376]

≪ Previous: Edited Issue: Analysis caused crash? [1375]

$

0

0

Using build 20903.00, VS 2013 Update 3
Edit: Not related to task explorer extension (repros without it)

Create starter express project.
Add new blank JavaScript file named grunt.js to project.
Close solution, save when prompted.
Reload solution and wait a few seconds.
If it doesn't repro, restart VS and reload solution.

```
Application: devenv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.InteropServices.SEHException
Stack:
at Microsoft.VisualStudio.Editor.Implementation.SimpleTextViewWindow.Init_InitializeWpfTextView()
at Microsoft.VisualStudio.Editor.Implementation.SimpleTextViewWindow.Init_OnActivation()
at Microsoft.VisualStudio.Editor.Implementation.SimpleTextViewWindow.get_WpfTextViewHost()
at Microsoft.VisualStudio.Editor.Implementation.SimpleTextViewWindow.GetData(System.Guid ByRef, System.Object ByRef)
at Microsoft.VisualStudio.Editor.Implementation.VsEditorAdaptersFactoryService.GetWpfTextViewHostFromVsTextView(Microsoft.VisualStudio.TextManager.Interop.IVsTextView)
at Microsoft.VisualStudio.Editor.Implementation.VsEditorAdaptersFactoryService.GetWpfTextView(Microsoft.VisualStudio.TextManager.Interop.IVsTextView)
at Microsoft.NodejsTools.Intellisense.VsProjectAnalyzer.GetOpenSnapshot(Microsoft.NodejsTools.Analysis.IProjectEntry)
at Microsoft.NodejsTools.Intellisense.VsProjectAnalyzer.ParseFile(Microsoft.NodejsTools.Analysis.IProjectEntry, System.String, System.IO.Stream)
at Microsoft.NodejsTools.Intellisense.VsProjectAnalyzer+<>c__DisplayClass6.<EnqueueFile>b__5()
at Microsoft.NodejsTools.Intellisense.VsProjectAnalyzer+<>c__DisplayClass9.<EnqueWorker>b__8(System.Object)
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()
```

Created Unassigned: Can't publish native node packages [1376]

September 4, 2014, 8:36 am

≫ Next: Commented Issue: Analysis caused crash? [1375]

≪ Previous: Edited Issue: Analysis caused crash? [1375]

$

0

0

Is it possible to deploy native #nodejs packages, eg level, on Azure websites? Node-gyp fails when continuous deployment is configured on Azure.

Commented Issue: Analysis caused crash? [1375]

September 4, 2014, 10:04 am

≫ Next: Created Issue: Can't create project if node isn't installed [1377]

≪ Previous: Created Unassigned: Can't publish native node packages [1376]

$

0

0

Using build 20903.00, VS 2013 Update 3
Edit: Not related to task explorer extension (repros without it)

Create starter express project.
Add new blank JavaScript file named grunt.js to project.
Close solution, save when prompted.
Reload solution and wait a few seconds.
If it doesn't repro, restart VS and reload solution.

```
Application: devenv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.InteropServices.SEHException
Stack:
at Microsoft.VisualStudio.Editor.Implementation.SimpleTextViewWindow.Init_InitializeWpfTextView()
at Microsoft.VisualStudio.Editor.Implementation.SimpleTextViewWindow.Init_OnActivation()
at Microsoft.VisualStudio.Editor.Implementation.SimpleTextViewWindow.get_WpfTextViewHost()
at Microsoft.VisualStudio.Editor.Implementation.SimpleTextViewWindow.GetData(System.Guid ByRef, System.Object ByRef)
at Microsoft.VisualStudio.Editor.Implementation.VsEditorAdaptersFactoryService.GetWpfTextViewHostFromVsTextView(Microsoft.VisualStudio.TextManager.Interop.IVsTextView)
at Microsoft.VisualStudio.Editor.Implementation.VsEditorAdaptersFactoryService.GetWpfTextView(Microsoft.VisualStudio.TextManager.Interop.IVsTextView)
at Microsoft.NodejsTools.Intellisense.VsProjectAnalyzer.GetOpenSnapshot(Microsoft.NodejsTools.Analysis.IProjectEntry)
at Microsoft.NodejsTools.Intellisense.VsProjectAnalyzer.ParseFile(Microsoft.NodejsTools.Analysis.IProjectEntry, System.String, System.IO.Stream)
at Microsoft.NodejsTools.Intellisense.VsProjectAnalyzer+<>c__DisplayClass6.<EnqueueFile>b__5()
at Microsoft.NodejsTools.Intellisense.VsProjectAnalyzer+<>c__DisplayClass9.<EnqueWorker>b__8(System.Object)
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()
```

Comments: With build 20904, I'm getting this crash now instead: ``` Application: devenv.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.InvalidOperationException Stack: at Microsoft.VisualStudio.Editor.Implementation.SimpleTextViewWindow.Init_OnActivation() at Microsoft.VisualStudio.Editor.Implementation.SimpleTextViewWindow.ShimHostNowVisible(System.Object, System.EventArgs) at Microsoft.VisualStudio.Editor.Implementation.SimpleTextViewWindow+TextViewShimHost.OnLayoutUpdated(System.Object, System.EventArgs) at System.Windows.ContextLayoutManager.fireLayoutUpdateEvent() at System.Windows.ContextLayoutManager.UpdateLayout() at System.Windows.ContextLayoutManager.UpdateLayoutCallback(System.Object) at System.Windows.Media.MediaContext+InvokeOnRenderCallback.DoWork() at System.Windows.Media.MediaContext.FireInvokeOnRenderCallbacks() at System.Windows.Media.MediaContext.RenderMessageHandlerCore(System.Object) at System.Windows.Media.MediaContext.RenderMessageHandler(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.DispatcherOperation.InvokeImpl() at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at System.Windows.Threading.DispatcherOperation.Invoke() at System.Windows.Threading.Dispatcher.ProcessQueue() at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) ```

---

Created Issue: Can't create project if node isn't installed [1377]

September 4, 2014, 3:23 pm

≫ Next: Created Issue: Wrap FileSystemWatcher to avoid race conditions [1378]

≪ Previous: Commented Issue: Analysis caused crash? [1375]

$

0

0

User should be able to create the project w/o node.js installed.

Created Issue: Wrap FileSystemWatcher to avoid race conditions [1378]

September 5, 2014, 12:35 pm

≫ Next: New Comment on "AzureWebSiteWebDeploy"

≪ Previous: Created Issue: Can't create project if node isn't installed [1377]

$

0

0

https://pytools.codeplex.com/workitem/2590

Create a fix that wraps FileSystemWatcher in our own class and implement an asynchronous Dispose(). If we queue the actual Dispose() on a background thread it can hang for as long as it likes until the program dies. The trick here is that we have to add a “IsDisposing” flag so we can recognise that we’re currently in this state, since otherwise there may be undetectable race conditions with file system events that are already in flight or come in before the Dispose completes.

New Comment on "AzureWebSiteWebDeploy"

September 5, 2014, 1:42 pm

≫ Next: Created Unassigned: Web.config and Web.debug.config will not deploy [1379]

≪ Previous: Created Issue: Wrap FileSystemWatcher to avoid race conditions [1378]

$

0

0

I created a new "Basic Microsoft Azure Express" application, and tried to publish it to my test Azure website. I get the following error: "------ Publish started: Project: ExpressApp4, Configuration: Release Any CPU ------ Auto ConnectionString Transformed Web.config into obj\Release\CSAutoParameterize\transformed\Web.config. Copying all files to temporary location below for package/publish: obj\Release\Package\PackageTmp. ========== Build: 0 succeeded, 0 failed, 1 up-to-date, 0 skipped ========== ========== Publish: 0 succeeded, 1 failed, 0 skipped ==========" I can publish individual files/folders, except for Web.config and Web.debug.config I tried with both 1.0 beta 2, and the Aug 13, 2014 dev release. Both result in the same error.

Created Unassigned: Web.config and Web.debug.config will not deploy [1379]

September 5, 2014, 1:46 pm

≫ Next: Commented Unassigned: Web.config and Web.debug.config will not deploy [1379]

≪ Previous: New Comment on "AzureWebSiteWebDeploy"

$

0

0

I created a new "Basic Microsoft Azure Express" application, and without changing the newly created project, I tried to publish it to a new test Azure website. I get the following error:

"------ Publish started: Project: ExpressApp4, Configuration: Release Any CPU ------
Auto ConnectionString Transformed Web.config into obj\Release\CSAutoParameterize\transformed\Web.config.
Copying all files to temporary location below for package/publish:
obj\Release\Package\PackageTmp.

========== Build: 0 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========
========== Publish: 0 succeeded, 1 failed, 0 skipped =========="

I can publish individual files/folders, except for Web.config and Web.debug.config

I tried with both 1.0 beta 2, and the Aug 13, 2014 dev release. Both result in the same error. Changing from "Release" to "Debug" doesn't help either.

Commented Unassigned: Web.config and Web.debug.config will not deploy [1379]

September 5, 2014, 1:52 pm

≫ Next: New Post: Project as blacklist manifest

≪ Previous: Created Unassigned: Web.config and Web.debug.config will not deploy [1379]

$

0

0

I created a new "Basic Microsoft Azure Express" application, and without changing the newly created project, I tried to publish it to a new test Azure website. I get the following error:

"------ Publish started: Project: ExpressApp4, Configuration: Release Any CPU ------
Auto ConnectionString Transformed Web.config into obj\Release\CSAutoParameterize\transformed\Web.config.
Copying all files to temporary location below for package/publish:
obj\Release\Package\PackageTmp.

========== Build: 0 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========
========== Publish: 0 succeeded, 1 failed, 0 skipped =========="

I can publish individual files/folders, except for Web.config and Web.debug.config

I tried with both 1.0 beta 2, and the Aug 13, 2014 dev release. Both result in the same error. Changing from "Release" to "Debug" doesn't help either.
Comments: I've attached the Diagnostic Info