Jonathan C.

My console app was working perfectly in debug mode through the IDE, but when I went to publish it for deployment on the server, out of nowhere I got 2 messages and an error.I am using DAAB 2, and I have the common, data, data.configuration DLLs referenced. I have another app which is a VSTO app, which after much effort works fine. I compared my config files and they virtually identical, so why am I getting the messages on 1 and not the other. (Deployment is a real SOB).

Anyway, I I got 2 messages and an error as follows. Any ideas would be extremely helpful. I have also posted the top of my app.config file.

Message 1 Could not find schema information for the element 'dataConfiguration'. C:\Documents and Settings\cohen\My Documents\Visual Studio 2005\Projects\PGIFTPDataProcessor\PGIFTPDataProcessor\app.config 14 3 PGIFTPDataProcessor

Message 2 Could not find schema information for the attribute 'defaultDatabase'. C:\Documents and Settings\cohen\My Documents\Visual Studio 2005\Projects\PGIFTPDataProcessor\PGIFTPDataProcessor\app.config 14 21 PGIFTPDataProcessor

Error 3 The "GenerateApplicationManifest" task failed unexpectedly.
System.IO.PathTooLongException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
at System.IO.Path.NormalizePathFast(String path, Boolean fullCheck)
at System.IO.Path.GetFullPathInternal(String path)
at System.IO.Path.GetFullPath(String path)
at Microsoft.Build.Tasks.Deployment.ManifestUtilities.Manifest.ResolvePath(String path, String[] searchPaths)
at Microsoft.Build.Tasks.Deployment.ManifestUtilities.Manifest.ResolveAssembly(AssemblyReference a, String[] searchPaths)
at Microsoft.Build.Tasks.Deployment.ManifestUtilities.Manifest.ResolveFiles_1(String[] searchPaths)
at Microsoft.Build.Tasks.GenerateManifestBase.ResolveFiles()
at Microsoft.Build.Tasks.GenerateManifestBase.BuildManifest()
at Microsoft.Build.Tasks.GenerateManifestBase.Execute()
at Microsoft.Build.BuildEngine.TaskEngine.ExecuteTask(ExecutionMode howToExecuteTask, Hashtable projectItemsAvailableToTask, BuildPropertyGroup projectPropertiesAvailableToTask, Boolean& taskClassWasFound) PGIFTPDataProcessor

My app.config file (top portion pertaining to messages)

< xml version="1.0" encoding="utf-8" >

<configuration>

<configSections>

<section name="dataConfiguration" type="Microsoft.Practices.EnterpriseLibrary.Data.Configuration.DatabaseSettings, Microsoft.Practices.EnterpriseLibrary.Data" />

</configSections>

<connectionStrings>

<add name="PGIFTPDataProcessor.My.MySettings.LocalConnection"

connectionString="Data Source=XPDEVELOPER;Initial Catalog=FOO2;Persist Security Info=True;User ID=xxxxx;Password=xxxxxxx"

providerName="System.Data.SqlClient" />

<add name="PGIFTPDataProcessor.My.MySettings.SammConnectionString"

connectionString="Data Source=SRV1\SRVNAME;Initial Catalog=FOO2;Persist Security Info=True;User ID=xxxxx;Password=xxxxxxx"

providerName="System.Data.SqlClient" />

</connectionStrings>

<dataConfiguration defaultDatabase="PGIFTPDataProcessor.My.MySettings.LocalConnection"/>


The names have been changed to protect the innocent.

Thanks



Re: Visual Studio MSBuild Console App blows up when I try to publish it. (GenerateApplicationManifest path too long)

Sampy MSFT

I can't help with the 2 messages but hopefully I can shed some light on the error.

The manifest generator is trying to resolve all of your references but one of them seems be located in a path that is too long. Can you double check the paths of all of your references just to make sure that they aren't the culprit

Thanks






Re: Visual Studio MSBuild Console App blows up when I try to publish it. (GenerateApplicationManifest path too long)

Jonathan C.

Is this path in my output directory, where I am going to publish the app Or is it having a problem with where my app is located now

Thanks!!!





Re: Visual Studio MSBuild Console App blows up when I try to publish it. (GenerateApplicationManifest path too long)

Sampy MSFT

It's having a problem with one of your references where they are now.




Re: Visual Studio MSBuild Console App blows up when I try to publish it. (GenerateApplicationManifest path too long)

Jonathan C.

Since I only had 2 modules in the app, I create a brand new project (with a much smaller name 6 chars instead of 30+) add the 2 modules and it worked and it published. I haven't had a chance to test it on the server yet. Stay tuned!

Thanks for all your help!

Jonathan





Re: Visual Studio MSBuild Console App blows up when I try to publish it. (GenerateApplicationManifest path too long)

Jonathan C.

Thanks for everyones help. My app works great. Though when I deployed it to the server, it put the application in a really funky location buried a couple of levels down in the Local Settings directory under one of my admin accounts. I'll figure this deployment stuff out eventually.

Again thanks.





Re: Visual Studio MSBuild Console App blows up when I try to publish it. (GenerateApplicationManifest path too long)

Cathie 64

Hi, Jonathan,

I noticed that you have successfully published your application (with application block). I am having problem with publishing my application, all my configuration files are not picking up by the publishing process for some reason. Do you know what can cause this problem, how to fix it

Thanks.

Cathie





Re: Visual Studio MSBuild Console App blows up when I try to publish it. (GenerateApplicationManifest path too long)

Cathie 64

Nerver mind, I fixed the problem.

Thanks.





Re: Visual Studio MSBuild Console App blows up when I try to publish it. (GenerateApplicationManifest path too long)

Luis Forero

How did you fix the problem




Re: Visual Studio MSBuild Console App blows up when I try to publish it. (GenerateApplicationManifest path too long)

Jonathan C.

Cathie, I apologize for not responding. After I got the answer I never returned to the thread. So I apologize if I left you hanging. BTW, I'm still having deplyment problems with the new version of my VSTO app. I hate this new security ***. My app is sooooo secure, nobody can even use it.



Re: Visual Studio MSBuild Console App blows up when I try to publish it. (GenerateApplicationManifest path too long)

Cathie 64

My configuration files were in a folder, I had to move them out to the root of the project.



Re: Visual Studio MSBuild Console App blows up when I try to publish it. (GenerateApplicationManifest path too long)

Cathie 64

No problem, Jonathan.

Happy coding!