[Fixed] Unable to Build Visualforce Page Changes

started by mark.a.filpus 10 Mar 2015 - 03:55 PM

Please log in to reply

#1

mark.a.filpus

Member
23 posts

Posted 10 Mar 2015

Hi,

I just downloaded this IDE and pulled in my project, but each time I try to build changes to a Visualforce Page, I get this error:

Error 80 Parameter "message" cannot be null. C:\Program Files (x86)\MSBuild\12.0\bin\Build.targets 6 6 Dev2

I'm able to build changes to classes successfully, but I'm not able to update Visualforce Pages. I'm also getting a bunch of warnings about "apex" being an unrecognized namespace, but I'm not sure if the two issues are related

Please let me know if you need any more info.

Thanks,

Mark

Edit: It looks like if I build the Solution rather than the selection, it will include the Visualforce page as long as there is also a change to an Apex class.

7 replies to this topic

#2

vlgubanovich

TWS Team
434 posts

Posted 10 Mar 2015

Hi Mark,

Thanks for detailed report and sorry for inconvenience caused - our team will investigate this issue asap.

Can you please answer some more questions so we can speed up investigation and fix:

Are you changing only VF page or both VF page and its controller before building?
Is there any custom components on the VF page you're trying to build? We've been experiencing some issues in this situation previously but were unable to reproduce them in the last version.

Regarding "apex namespace" warnings - we'll add suppression of this warnings to one of our next releases as well.

I'll keep you updated with our investigation and fix status.

If you'll have any questions regarding The Welkin Suite or if you'll experience any issues - please feel free to let me know via email or here on the forum.

Thanks,

Vladimir

Vladimir Gubanovich
Head of Product

The Welkin Suite
skype id: vladimir.gubanovich
e-mail: vladimir.gubanovich@welkinsuite.com

#3

mark.a.filpus

Member
23 posts

Posted 10 Mar 2015

Hi Vladimir,

Thanks for the quick reply.

1. If I change the Visualforce page alone, I get the error message. If I change the page and its controller, I am able to build the Solution, and both changes are committed correctly.

2. Yes, there is a custom component in the page I was having issues with. I just tried building a different VF page with no components, and it built successfully without needing to update the class as well, so that's looking like a good place to start.

Great news on suppressing the Unrecognized Namespace warnings.

Thanks for your help so far!

Thanks,

Mark