-
8 Apr 2009 7:49 AM #1
[FIXED] [3.0] ext-core and visual studio 2008
[FIXED] [3.0] ext-core and visual studio 2008
There seems to be some issue with the recently released beta of ext-core as well as the latest from svn that makes the file not play "nice" with Visual Studio.
If you include the ext-core.js or ext-core-debug.js in the body of html document IE7 gives a "line 1008: _load is null and not or not an object error". If you include the script in the head you get an error in the Visual Studio IDE that makes intellisense fail completely in any place that the file is referenced.
"Warning 1 Error updating JScript IntelliSense: C:\TFS\VS2008\Shapes\Shapes\js\ext-core-debug.js: '_load' is null or not an object @ 1007:20 C:\TFS\VS2008\Shapes\Shapes\Default.aspx 1 1 Shapes"
Any idea what the issue might be? Thanks!Jon
-
8 Apr 2009 8:21 AM #2
Thanks for the report, we'll take a look into it.
Aaron Conran
@aconran
Sencha Architect Development Team
-
8 Apr 2009 8:40 AM #3
Oh yeah, I don't use Visual Studio, but I can't get any Ext3 code to work on IE without commenting out that line. I never ported my changes to onReady over since the code is different. I'd like not to... still have to fix mask first, higher priority.
-
8 Apr 2009 10:31 AM #4Sencha - Sencha Touch Dev Team
- Join Date
- Mar 2007
- Location
- Haarlem, Netherlands
- Posts
- 1,235
- Vote Rating
- 5
It was an error that happened when you would include ext inside the body instead of the <head>.
I fixed it in SVN.
-
9 Apr 2009 5:28 AM #5
Just pulled the latest from SVN and built everything with JSBuilder and noticed no change from what I reported earlier. Same error at the same line number.
I like to include the script files in the body right before the closing </body> tag because I can use an include directive to pick the appropriate file based on the project build type settings.
PHP Code:<% #if DEBUG %>
<script src="js/ext-core-debug.js" type="text/javascript"></script>
<% #else %>
<script src="js/ext-core.js" type="text/javascript"></script>
<% #endif %>
Jon
-
10 Apr 2009 7:57 AM #6
It does appear to be fixed!
It does appear to be fixed!
This does appear to be fixed now.
I got tripped up because the output directory of the .jsb file changed from c:\apps\www... to c:\www\shared...
I've been pulling my files from the original directory for at least 2 years!
SHAME on whoever changed to path!!!!!!
Jon
-
12 Apr 2009 7:06 AM #7
No way
No way
I am not Ext JS Premium Member, wait for the next version.
-
15 Apr 2009 6:54 PM #8
I am not Ext JS Premium Member, wait for the next version.

-
15 Apr 2009 8:38 PM #9
Umm... the next version was released this morning. Did you try it?
Tim Ryan
Read BEFORE posting a question / BEFORE posting a Bug
Use Google to Search - API / Forum
API Doc (4.x | 3.x | 2.x | 1.x) / FAQ / 1.x->2.x Migration Guide / 2.x->3.x Migration Guide
Thank you for reporting this bug. We will make it our priority to review this report.


Reply With Quote
